My thinking has changed on browser compositors a bit: they’re a necessary evil, but they should be treated as a power savings optimization (primarily when scrolling is involved), not as the way to get fast animations.
For example, in an OS where the browser had exclusive access to the GPU and display, I wouldn’t be inclined to go with a compositor. Just use WebRender directly.
-
-
But on Windows, macOS, and Linux with Wayland subsurface support, you can save the OS a full window blit if you divide your page up into tiles or something and do partial presents. Basically this is because OS compositors are too simple to handle CSS in its full generality.
-
Or, another way to look at it: On typical OS’s you’ve got a compositor sitting there whether you want it or not. Might as well make the best use of it you can.
End of conversation
New conversation -
-
-
Oh cool! Sounds like you are doing power benchmarks! Excited to see the results
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.