Perfect example of how doubling down on paint/compositor hurts the Web https://developers.google.com/web/updates/2017/03/performant-expand-and-collapse … — why do we put devs through so much pain?
-
-
Replying to @pcwalton
Instead of shaming developers, we as browser vendors should think about how we can make the simple, obvious thing also the fast thing.
2 replies 7 retweets 26 likes -
Replying to @pcwalton
I don't see any shaming in that post, but I'd like to see clip-path moved to the compositor to make this easier https://bugs.chromium.org/p/chromium/issues/detail?id=686074 …
3 replies 0 retweets 0 likes -
Replying to @jaffathecake
Let’s just kill the compositor. We should move width and height off the main thread too.
1 reply 0 retweets 0 likes -
Replying to @pcwalton
Layout is synchronously accessible by JS — not sure how it can be moved off the main thread
2 replies 0 retweets 0 likes
The way Servo does it. :) Do layout solely on the render tree. Layout queries from JS send messages to request results.
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.