: this will always be slower. You're defeating all of our parser opportunities, to start with. It's a bad idea.
-
-
Apparently recalcs when adding new sheets is a big cost for us. Per-element styles seem to solve that.
1 reply 0 retweets 0 likes -
Replying to @sophiebits @soprano and
We're working on making inserting sheets faster, definitely something we're fixing.
1 reply 0 retweets 3 likes -
btw you insert 85+ stylesheets on page load on http://facebook.com , batching would help you too :P
1 reply 0 retweets 1 like -
That has other downsides which is why we don't.
1 reply 0 retweets 0 likes -
Replying to @sebmarkbage @ElliottZ and
Is the reason you don't want to add the JS API that you worry JS parse time will be worse than CSS parse?
1 reply 0 retweets 0 likes -
Replying to @sebmarkbage @ElliottZ
: much of the setting overhead will be taken care of w/ CSS Typed OM: https://www.w3.org/TR/css-typed-om-1/ …
1 reply 0 retweets 1 like -
I don't remember if Blink is one of them, but some engines use shared data structures. E.g. sibling styles.
1 reply 0 retweets 0 likes -
Replying to @sebmarkbage @slightlylate and
For example Firefox uses a string map to reuse the same object from multiple equivalent cssText values.
1 reply 0 retweets 0 likes -
Replying to @sebmarkbage @slightlylate and
Will this enable the same thing?
1 reply 0 retweets 1 like
: it largely removes parsing overhead from property setting.
-
-
Yes, Blink does sharing. http://e.style = immutableObject doesn't allow more sharing.
1 reply 0 retweets 1 like -
Replying to @ElliottZ
More than CSS rules? It'd allow more sharing than Object.assign(http://e.style , immutableObject);?
@slightlylate@soprano1 reply 0 retweets 0 likes - 3 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.