Incomplete List of Mistakes in the Design of CSS
here's my pet peeves:<p>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.<p>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 <i>relationships</i> <i>between</i> 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.<p>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?<p>3. The naming of properties and values is entirely inconsistent. Sometimes "none" works. sometimes it doesn't. What even <i>is</i> going on with "white-space"?<p>4. Who allowed Microsoft to add "pointer-events" properties to css? This is a tragedy.<p>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.