On macOS, Firefox’s entire window is marked as non-opaque to the compositor and gets fully presented on every event. Chrome has neither issue, probably part of the battery life gap. FF is otherwise quite nice so far though! cc @pcwalton
-
-
Replying to @trishume
Isn’t Chrome using Core Animation these days on macOS?
1 reply 0 retweets 1 like -
Replying to @pcwalton
They at least at one point used this hack FF could steal for using a CALayer to partial present a GL surface: https://bugs.chromium.org/p/chromium/issues/detail?id=474299 …. Did they switch to using full CALayer based compositing at some point? If so, do you have a link?
1 reply 0 retweets 0 likes -
Replying to @trishume
I dunno, I just heard that Chrome uses full CA at the all hands. Didn’t verify; could be wrong.
1 reply 0 retweets 0 likes -
Replying to @pcwalton
Looks like you’re right. I found this: https://cs.chromium.org/chromium/src/ui/accelerated_widget_mac/README … and the --show-mac-overlay-borders flag. That code also has a bunch of helpful comments about gotchas in the CA API. During my journey I even found hints of the driver bug I encountered earlier (I edited the WR wiki).
1 reply 0 retweets 0 likes
BTW, we’re planning on using Core Animation with WebRender too for scrolling. Would be happy to talk more if you’re interested :)
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.