Absolutely you may have seen a CSS property and thought “Why?” For instance:
Why doesn’t
z-indexwork on all components, and why is it “-index” anyhow?
Or:
Why do we want
interpolate-sizeto animate toauto?
You aren’t alone. CSS was born in 1996 (it may legally order a beer, you already know!) and was initially thought-about a technique to fashion paperwork; I don’t suppose anybody imagined every little thing CSS can be anticipated to do practically 30 years later. If we had a time machine, many issues can be completed in a different way to match conventions or to make extra sense. Heck, even the CSS Working Group admits to wanting a time-traveling contraption… within the specs!
NOTE: If we had a time machine, this property wouldn’t must exist.
CSS Values and Models Module Degree 5, Section 10.4
If by some stroke of alternative, I used to be given free rein to rename some issues in CSS, a few concepts come to thoughts, however if you would like extra, yow will discover an ongoing record of errors made in CSS… by the CSS Working Group! Take, for instance, background-repeat:
Not fairly a mistake, as a result of it was an inexpensive default for the 90s, however it might be extra useful since then if
background-repeatdefaulted tono-repeat.
Proper now, individuals are questioning if CSS Flexbox and CSS Grid should share more syntax in mild of the upcoming CSS Masonry layout specifications.
Why not repair them? Sadly, it isn’t as straightforward as fixing one thing. Individuals already constructed their web sites with these quirks in thoughts, and altering them would break these websites. Take into account it technical debt.
For this reason I feel the CSS Working Group deserves an onslaught of reward. Designing new options which can be immutable as soon as shipped must be a nerve-wracking expertise that entails inexact science. It’s not that we haven’t seen the specs change or evolve up to now — they most definitely have — however the worth of getting issues proper the primary time is a beast of burden.
