i'm saying that it's easier for the browser to figure out how to paint an element if it only has to worry about a few local styles, rather than seeing which of the global ones are relevant and doing the specificity dance
Again, that's backwards. You inline your component definitions such that they evaluate before use; voila, no upgrade!
-
-
Surely that means introducing render-blocking JavaScript, and a broken page if the JS fails for whatever reason? For sites that don't expect the user to interact immediately beyond scrolling (e.g. news sites), that feels like a step backwards to me
-
This whole conversation is surreal to me. You can do any of: a.) SSR in a WC-aware way (Rendertron) and then you're doing what JS-driven UI does today b.) inline critical components the way we inline CSS c.) design placeholder CSS for components
- 6 more replies
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.