Incomplete List of Mistakes in the Design of CSS
wiki.csswg.org
Incomplete List of Mistakes in the Design of CSS
1–10 of 154 posts
Re: Incomplete List of Mistakes in the Design of CSS
#2Some of these seem very nit picky but if we are doing that my pet peeve was that the “color” property should have been named “text-color”
Re: Incomplete List of Mistakes in the Design of CSS
#3Some of these seem very nit picky but if we are doing that my pet peeve was that the “color” property should have been named “text-color”
Or just "font-color" to match font-face and font-family. etc. That still gets me almost every time.
Re: Incomplete List of Mistakes in the Design of CSS
#4Some of these seem very nit picky but if we are doing that my pet peeve was that the “color” property should have been named “text-color”
Or just "font-color" to match font-face and font-family. etc. That still gets me almost every time.
Color is not a property of font so I'd stick with "text-color"
Re: Incomplete List of Mistakes in the Design of CSS
#5(1) it should have been designed around what people actually try to do: three column layouts with headers and footers, aligning content in the middle, pinstriping (this one isn’t as popular anymore), drop shadows, etc. Instead, all of these things required either hacky workarounds, or stepping outside of CSS entirely. The first decade of CSS was “look at all these things you can do that you don’t want to, and you can use them so long as you don’t try to make the kind of sites your clients actually ask for!" So fucking stupid, it still makes me angry years later.
Re: Incomplete List of Mistakes in the Design of CSS
#6here'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 really icky hacks and implied relationships in a language like CSS, e.g. the definition of percentage units (percentage of what?) being mostly arbitrary and context sensitive, So you are forced to learn what all those context rules are to get the desired outcome.
What does height: 80% mean? 80% of the parent element's width? 80% of the parent element's height? 80% of the window width? who knows?
3. The naming of properties and values is entirely inconsistent. Sometimes "none" works. sometimes it doesn't. What even is going on with "white-space"?
4. Who allowed Microsoft to add "pointer-events" properties to css? This is a tragedy.
5. em based font sizing seems like a really good idea until you use it in some system that will arbitrarily nest component elements until the innermost reply to a comments thread is either microscopic or 3 characters per line.
Re: Incomplete List of Mistakes in the Design of CSS
#7(1) it should have been designed around what people actually try to do: three column layouts with headers and footers, aligning content in the middle, pinstriping (this one isn’t as popular anymore), drop shadows, etc. Instead, all of these things required either hacky workarounds, or stepping outside of CSS entirely. The first decade of CSS was “look at all these things you can do that you don’t want to, and you can…
> three column layouts with headers and footers
I was appalled when I saw what was needed to make this use case, used by 1/2 he web pages in existence.
Re: Incomplete List of Mistakes in the Design of CSS
#8Re: Incomplete List of Mistakes in the Design of CSS
#9Earlier quoted context omitted.
Or just "font-color" to match font-face and font-family. etc. That still gets me almost every time.
Color is not a property of font so I'd stick with "text-color"
In practice it usually is part of the same font selection dialog in most software that you use to select the font face, size, bold/italic/underline, etc.
For example, the relevant button in Word is titled "Font Color"
Re: Incomplete List of Mistakes in the Design of CSS
#10Earlier quoted context omitted.
Or just "font-color" to match font-face and font-family. etc. That still gets me almost every time.
Color is not a property of font so I'd stick with "text-color"
Hold on a second here! It actually becomes the "currentColor" color in inlined SVGs, and the default fill color in svg when no color is defined. so oops, not a property strictly of text or fonts anymore. Maybe "foreground-color" would be appropriate?