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.
1
8
But it also gives first-class control to the developer when using third-party components and libraries.
2
1
As a dev who is often hired to work on Bootstrap-born (or other third-party libs/components) sites after the fact (and who knows the cascade and inheritance), I no longer have to mimic the stupid-long selector I need to override.
1
1
Replying to @LiveLongAndCSS
I understand that especially when you have large sites with multiple origin CSS that has enough conflicts to take so much extra time to resolve without the CSS important declaration. Also common in Legacy that is not portable in any way and should be easily portable if it is web.

Apr 25, 2022 路 11:15 AM UTC

3
1
Replying to @mholzschlag @LiveLongAndCSS
What do I have an especially hard time with however is how come the CSS got that problematic if the people writing it in the first place understood the Cascade understood how to write appropriate selectors and how to deal with multiple origin Style, specificity and sort order.
1
Replying to @mholzschlag @LiveLongAndCSS
So there is a realistic issue about how to deal with Legacy code. I think there's a lot of room to stabilize code properly, reduce CSS to Origins not have to rewrite algorithms and better separate scripting that is obscuring content, setting up that site for longer-term easy care
1
Replying to @mholzschlag @LiveLongAndCSS
Of course this takes some time but I would bet money on the fact that if that's a long-lasting site it's going to be a lot easier and take a lot less money and time in the future as changes get made because you simplified the structure of the site.
1
1
more replies