CSS WG level 4 and 5 module changes due to misuse of !important with layer which while not illogical as a solution to external frameworks causing language fragmentation and rushing solutions instead of collaborative, evolving WG specs is reactionary, not innovative. Bothers me.

Apr 24, 2022 路 7:30 AM UTC

1
8
Replying to @mholzschlag
But it also gives first-class control to the developer when using third-party components and libraries.
2
1
I see the advantage of that as well except the portability again becomes a problem so does scaling and so does reaching the widest possible audience. By forcing languages that aren't were not meant to build applications to work together to do so has really poor logic behind it's.
1
This tweet is unavailable
Preaching it my sister you know I'm flashing back to the last time we saw each other in Massachusetts and how we both were really unhappy with the use inline style the CSS Cascade, inheritance and specificity sucks etc etc. I'm still in shock from that and that was 2016?
1