are there any efforts underway to rectify the horror of css?
When it comes to widely-used web standards, we tend to be pretty much stuck with them forever. They get extended, but not replaced.
Incomplete List of Mistakes in the Design of CSS
91–100 of 154 posts
Re: Incomplete List of Mistakes in the Design of CSS
#92Wow I just started making websites of my own recently and have encountered so many things that are immensely infuriating about how the language is interpreted that I've been thinking about starting a list myself. They seem to favor implied behavior rather than explicitly defined behavior which is incredibly annoying. For example, space between inline-block elements that is not accounted for by margins. The fact that…
I often feel annoyed too but CSS what we have been given to work with. Instead of wasting time being annoyed that reality does not match our expectations it is better for our health to swallow the bitter (red?) pill, accept reality and learn CSSs idiosynchracies. The page http://book.mixu.net/css/ shoud help.
Re: Incomplete List of Mistakes in the Design of CSS
#93CSS should have used linear color space for gradients and blending instead of sRGB. I don't want CRT emulation in 2018.
https://lists.w3.org/Archives/Public/www-style/2012Jan/0615....
Re: Incomplete List of Mistakes in the Design of CSS
#94Earlier quoted context omitted.
It never worked well in the original envisaged usecase. CSS 1 didn’t work properly with tables which meant I used to have to inline style attributes for tables as well as set a CAS file. It’s always been garbage for centering things, in the early days that meant using the tag. Then you have all the different browser extensions (o-, mo-, etc) the inconsistent preferences for font-face, etc. CSS was a great idea but it…
Learn CSS Layout the pedantic way at: http://book.mixu.net/css/ can help with the trial and error bit. It impossible to get an intuitive feel for nearly 400 keywords IMHO.
That's great reference (thank you for the link) but one of the great - if not the single greatest - accomplishments of the web was that it allowed anyone with a text editor and access to the internet to publish content with ease. I get that commercialisation of any platform will lead to specialities in that field; however the tools shouldn't make it objectively harder for new comers to contribute. Let alone discriminate against hobbyists who might not want to spend several hours of their life learning CSS (never-mind HTML, perhaps Javascript, how cookies work and any regional legislations, OWASP should they dare to have any user submission forms, etc).
Talking personally, I published my first website in 1994 when there wasn't different layout modes. Now it is suggested that I read a multi-chapter book just to learn what's changed in CSS so I can publish the same content I had before but in a "web 3.0" (for want a better description) format.
I appreciate my comments are very ranty / preachy and do value your comment as I hadn't seen that link before; so my comments are not directed at you in any negative way at all! What I'm essentially just trying to say is web development has become very frustrating for anyone outside of the webdev community. Heck, I find it frustrating and I used to specialise in hardening web servers so have worked quite close to that community.
Re: Incomplete List of Mistakes in the Design of CSS
#95Earlier quoted context omitted.
> Try setting a child of a flexbox container to 100% height. Isn't this the default? align-items: stretch --- https://css-tricks.com/snippets/css/a-guide-to-flexbox/ > The days of needing separate constructs because of bandwidth are over That wasn't the reason for stylesheets. It was for ease of changes. For example, to change the color of the headings on all of your HTML pages, you would change just the stylesheet.…
https://stackoverflow.com/questions/33636796/chrome-safari-n... I'm referring to this. Got bitten by it recently. > That wasn't the reason for stylesheets. It was for ease of changes. For example, to change the color of the headings on all of your HTML pages, you would change just the stylesheet. This was when each web page was a static HTML file. Few websites used programming languages to render pages. So the benefi…
Back when CSS was useful for changing the color of all your headlines without changing all your HTML, it wasn't delivered in giant minified files, it was a couple dozen lines written by hand.
Re: Incomplete List of Mistakes in the Design of CSS
#96Earlier quoted context omitted.
If that's a serious problem for you, setup your vim to use a different color for variables based on the current filetype.
It’s not a serious problem to work around, but it is another instance where the web architects designed all these different languages without thinking all that deeply about how they would work together. and so i need .style[“background-color”] .style.width=mywidth+”px” and (sigh) href=“/search?q=hello%20world&another=query%20parameter” the latter of which is, while it's the correct way to write html, is so stupid…
Can you explain why it's technically wrong?
Re: Incomplete List of Mistakes in the Design of CSS
#97Wow I just started making websites of my own recently and have encountered so many things that are immensely infuriating about how the language is interpreted that I've been thinking about starting a list myself. They seem to favor implied behavior rather than explicitly defined behavior which is incredibly annoying. For example, space between inline-block elements that is not accounted for by margins. The fact that…
I often feel annoyed too but CSS what we have been given to work with. Instead of wasting time being annoyed that reality does not match our expectations it is better for our health to swallow the bitter (red?) pill, accept reality and learn CSSs idiosynchracies. The page http://book.mixu.net/css/ shoud help.
While reading that page, it is helpful to make flashcards like you are a med student. In fact "flashcards are a good idea" is probably a good piece of advice for gaining a mental model of a system which was the result of more incremental evolution than all-at-once intelligent design.
Re: Incomplete List of Mistakes in the Design of CSS
#98A new software engineering maxim: "The bar of complaint will rise to meet any improvements"
Nah, I've definitely used some software which had fantastic cognitive affordances, fit in my working memory really easily, and which people broadly agreed were fantastic.
Re: Incomplete List of Mistakes in the Design of CSS
#99here's my pet peeves: 1. CSS should not have adopted a hyphenated naming scheme for properties, since it makes it difficult to access css properties from javascript or other languages. 2. CSS should never have been used for layout, and nobody should have suggested it should be. CSS defines properties on individual elements, while layout fundamentally needs to define relationships between elements, which requires real…
I came here to post what you already did on (2)
Couldn't agree more.
The problem is that we are stuck with it, looks like web technologies are set in stone.
Here's how it should have been:
Re: Incomplete List of Mistakes in the Design of CSS
#100Earlier quoted context omitted.
From the beginning, CSS tutorials said just what you said, that the web is not the printed page and that you should not strive for pixel-perfect layout.
Which is exactly what anyone that I've talked to that gets paid to write CSS in any aspect is expected to do with it; pixel-perfect layouts.
I already had the "pleasure" of being in a project whose customer was refusing to pay as it was pixel perfect with their Powerpoint designs and across all major browsers and OSes. :(