Is the reason you don't want to add the JS API that you worry JS parse time will be worse than CSS parse?
-
-
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 -
Replying to @sebmarkbage @ElliottZ
: it largely removes parsing overhead from property setting.
1 reply 0 retweets 1 like -
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 -
Not really, you need to inherit from the same parent, have the same attributes, etc. sharing is hard.
1 reply 0 retweets 1 like -
Replying to @ElliottZ
Seems like a valuable thing to make easier, no? E.g. by limiting inherited scoped things.
@slightlylate@soprano2 replies 0 retweets 0 likes
: CSS scopes via DOM. The way to change that is to change scope of DOM (hence Shadow DOM).
/cc @ElliottZ @soprano
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.