(In reply to Andrew Osmond [:aosmond] from comment #5) > One open question I have then is if Wayland is sufficiently stable (or we anticipate it will reach such in time for a train) that we won't care to test/ship the XWayland + WebRender configuration? Wayland backend is disabled by default, that's covered by Bug 1543600, and we're not going to enable it anytime soon as Wayland does not work with flash plugin and we don't have a test stuite finished yet (Bug 1578640). Wayland is enabled by default on some specific distros like Fedora where the Wayland backend is developed. So I think it's safe to enable WR on Wayland and test/develop that configuration togethter.
Bug 1675768 Comment 8 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Andrew Osmond [:aosmond] from comment #5) > One open question I have then is if Wayland is sufficiently stable (or we anticipate it will reach such in time for a train) that we won't care to test/ship the XWayland + WebRender configuration? Wayland backend is disabled by default, that's covered by Bug 1543600, and we're not going to enable it anytime soon as Wayland does not work with flash plugin and we don't have a test stuite finished yet (Bug 1578640). Wayland is enabled by default on some specific distros like Fedora where the Wayland backend is developed. So I think it's safe to enable WR on Wayland and test/develop that configuration togethter. Note: Also Wayland is enabled on Fedora/Gnome only where it's well tested, not on KDE.