Yep. It's why Shadow DOM matters.
-
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
Replying to @treshugart @johnallsopp and
As I've said frequently: I don't care how you write your styles, but for the love of everything holy, don't bake them into your script bundles for deployment.
0 replies 1 retweet 4 likes -
This Tweet is unavailable.
-
Replying to @treshugart @johnallsopp and
Can still clone style blocks from elsewhere. Imports were better at this (had other, fixable, problems tho).
0 replies 0 retweets 1 like -
This Tweet is unavailable.
-
Replying to @treshugart @johnallsopp and
When styles are pulled in late (as happens with naive CSS-in-JS), we lose load-time parallelism and double memory footprint.
1 reply 0 retweets 1 like -
Replying to @slightlylate @treshugart and
Once styles are parsed/in-DOM, we dedupe across SD instances. Question here is about loading: did the styles get sent as <style> in, e.g., a <template>? Or are they being appendChild()'d at runtime via script?
2 replies 0 retweets 2 likes -
Replying to @slightlylate @treshugart and
Separate issue is classes vs inline. Classes are clearly better.
1 reply 0 retweets 1 like
Anyway, this *might* be small potatoes in memory terms depending on app. Reducing # of layers & killing leaks almost always has a bigger impact.
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.