I inadvertently created a litmus test for reasonable windowing APIs: whether you can reposition two HW graphics surfaces simultaneously without tearing, using only public API. Windows Vista+, macOS 10.7(?)+, Wayland: Pass X11, Android (all versions!): Fail.
There will be a fallback compositor for unsupported systems, so WR will still work fine. It’ll just be less power efficient.
-
-
Is Wayland already supported in WR or is it planned?
-
Firefox runs in Xwayland currently, and WebRender works in Xwayland on Nightly builds currently. Mozilla doesn't provide a native Wayland build currently, so it isn't as optimized for Wayland at the moment as it is for X11. Looking forward to a native Wayland build.
-
Note that I don’t think going through Xwayland is really any less efficient than going through native Xorg would be. The main thing is that I want to take advantage of Wayland subsurfaces for energy savings, which requires using Wayland directly.
- 1 more reply
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.