Question for browser vendors: Is there anything slow about the DOM rendering lifecycle that's due to backwards compatibility (ie. not breaking random websites)?
-
-
Replying to @hugoccampos @sebmck
I don't
@v8js is significant part of the problem here. But I'm also not sure what counts as part of "the DOM rendering lifecycle". This probably needs attention from experts. cc@addyosmani@jaffathecake@samccone@slightlylate1 reply 0 retweets 3 likes -
Replying to @bmeurer @hugoccampos and
We’d do things differently if we could. Attribute/property split (introduced by Netscape/IBM) has made lots of things harder.
1 reply 0 retweets 6 likes -
Replying to @slightlylate @bmeurer and
The “rendering lifecycle” is a very deep topic. I’d of course love better layering and a chance to revisit the threading model. Doing our I/O on the main thread is a bug.
2 replies 0 retweets 12 likes
Good news is Houdini APIs are breaking up the monopoly that CSS has on lots of this. 2018 will be transformative.
-
-
- 2 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.