As a browser person, I bet you have some pretty wild reasons for not being a fan of CSS!
-
-
Replying to @brad_frost @davidbrunelle
No man, I just hate global variables ;-) But seriously, Shadow DOM is the answer to CSS in the same way that "structured programming" is the answer to assembly.
4 replies 0 retweets 7 likes -
Can you expound a little, my friend? I struggle with this...
1 reply 0 retweets 1 like -
CSS w/o Shadow DOM puts all rules and all elements into the same namespace for rule resolution. This creates all sorts of problems; specificity breaks down at scale.
1 reply 0 retweets 5 likes -
Replying to @slightlylate @stefsull and
Shadow DOM is like a function: local stuff is local, which reduces burden on global namespace while making internal concerns easier to reason about.
1 reply 0 retweets 5 likes -
Yes, that I understand. It was your Assembly reference. ;) Regardless, I've helped architect a CSS framework for an Enterprise company using principles that have avoided the things that scare y'all about CSS.
1 reply 0 retweets 4 likes -
Replying to @stefsull @slightlylate and
But Shadow DOM works opposite of how a well-architected framework works. And it's not compatible in many ways.
2 replies 0 retweets 3 likes -
Replying to @stefsull @slightlylate and
It feels like making it all local takes the C out of CSS. In fact, in some ways it kinda reverses it. CSS is really okay. It's not an untamed beast, just a different, very powerful beast. Whatever. It is what it is. I just wish we could finish that spec about theming. ;)
1 reply 0 retweets 4 likes -
I think of it as returning CSS to what it's good at: styling small trees. By making components responsible for their own internal
state, reduce the "bleed through" that makes managing styles so painful.
Good progress being made on part/theme: https://www.chromestatus.com/feature/5763933658939392 …2 replies 0 retweets 2 likes -
Replying to @slightlylate @stefsull and
And is CSS really ok? There has been an explosion of tools whose primary value is that they turn off specificity and the cascade (Inc CSS-in-JS tools). Teaching the "C" is a nightmare. Folks rightly want fewer foot-guns.
4 replies 0 retweets 5 likes
@ojanvafai and I have discussed a feature policy to disable descendant selectors. It'd enable some pretty big perf wins, but more importantly, it might make CSS livable again (particularly in combination with SD)
-
-
Replying to @slightlylate @brad_frost and
We keep selectors as flat as possible. But when we use descendants, there's usually a good reason (table markup, changing overall form layout, a class that indicates a small space since container queries will never happen). Siblings are another important one in certain situations
1 reply 0 retweets 0 likes -
Replying to @stefsull @slightlylate and
Scroll down to where it says "element queries"
They're on the roadmap!
https://www.w3.org/2018/04/web-roadmaps/mobile/adaptation.html …0 replies 0 retweets 0 likes
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.