-
If you (like me & most CSS authors) are used to thinking ofPermalink On twitter.com
!importantas a specificity-override – then the new layer-reversal behavior is extremely confusing. It's not designed for that use-case. We can now use Cascade Layers w/o importance to manage overrides. Which means…♻️ 17 Retweets ❤️ 110 Favorites Mood +4 🙂
-
That's not the intended use-case for layer-reversal! Instead, we consider the use thatPermalink On twitter.com
!importantwas designed for, and where it is still needed. Marking some declarations as *required* for a selector pattern to work, even when the selector is otherwise low-powered. -
In that situation, which browser styles & user preferences already rely on, the reversal of origins is a great solution to the problem. And when we extend that use-case into a single origin, it also becomes a useful tool for layers.On twitter.com
-
So it can be simultaneously true that this behavior is Extremely Confusing (from one perspective, which we hope to deprecate) and also Extremely Sensible (from another perspective we hope to encourage).Permalink On twitter.com
-
I hope authors take the time to learn this new feature, because I think people will find it quite useful as-designed. But yes, it will take some time (and sometimes a bit of confusion) to learn a new mental model, and transition our code to a new way of working.Permalink On twitter.com