1543600 - (wayland-nightly) [meta] Enable Wayland by default on nighly & qualified systems

Status: RESOLVED FIXED

(Core :: Widget: Gtk, task, P3)

Description

[Martin Stránský [:stransky] (ni? me)]

We should consider to enable Wayland on nightly and qualified systems (recent Gtk + gnome-shell/mutter compositor). It also needs some remaining bugs fixed.

Comment 1

[Laurențiu Nicola]

I think this should block on bug 1508803, which makes Firefox unusable for normal browsing. Switching to the window and clicking on links doesn't work because of it.

Comment 2

[Martin Stránský [:stransky] (ni? me)]

(In reply to Laurentiu Nicola from comment #1)

I think this should block on bug 1508803, which makes Firefox unusable for
normal browsing. Switching to the window and clicking on links doesn't work
because of it.

When you set nightly as a default browser (and the nightly is wayland enabled) the bug 1508803 is automatically fixed for you.

Comment 3

[Sawyer Bergeron]

This seems like it should depend on bug 1478283, but I'm not sure if the KDE userbase is large enough to warrant a block on all platforms. Thoughts?

Comment 4

[Martin Stránský [:stransky] (ni? me)]

(In reply to Sawyer Bergeron from comment #3)

This seems like it should depend on bug 1478283, but I'm not sure if the KDE
userbase is large enough to warrant a block on all platforms. Thoughts?

It can be enabled on mutter (gnome) only.

Comment 5

[Martin Stránský [:stransky] (ni? me)]

Main blocker here is flash which does not work under Wayland.

Comment 6

[nickp]

(In reply to Martin Stránský [:stransky] from comment #5)

Main blocker here is flash which does not work under Wayland.

Is Flash not working under anything really a blocking problem? Its set to be officially deprecated in 2020 and Adobe and many others have already pushed for removal of it.

I'm honestly curious. If there is something i'm not considering.

Comment 7

[Martin Stránský [:stransky] (ni? me)]

(In reply to nickp from comment #6)

(In reply to Martin Stránský [:stransky] from comment #5)

Main blocker here is flash which does not work under Wayland.

Is Flash not working under anything really a blocking problem? Its set to be officially deprecated in 2020 and Adobe and many others have already pushed for removal of it.

I'm honestly curious. If there is something i'm not considering.

I don't want to regress any major functionality that X11 Firefox version provides, that will cause lot of confusion among users.

Comment 8

[Darkspirit]

IMHO, Flash removal should no longer block enabling Wayland on Nightly/Gnome because:

• Someone who wants this kind of legacy stuff could simply login to an X11 desktop session
• Wayland is already enabled in the Flatpak build: bug 1628406
• Mozilla would force-disable Flash for Fission as well: bug 1129492 comment 26

Comment 9

[Mike Hommey [:glandium]]

(In reply to Jan Andre Ikenmeyer [:darkspirit] from comment #8)

• Someone who wants this kind of legacy stuff could simply login to an X11 desktop session

I'm not particularly convinced we can rely on people being able to do that on their own.

• Wayland is already enabled in the Flatpak build: bug 1628406

I don't think that's true. That bug only made the wayland socket available to the flatpak. I don't think the Firefox binary in the flatpak will use wayland by default. That would actually require this bug to be fixed to happen.

• Mozilla would force-disable Flash for Fission as well: bug 1129492 comment 26

Which means we /could/ enable wayland automatically if fission is enabled.

Comment 10

[Martin Stránský [:stransky] (ni? me)]

Before any Wayland enablement Bug 1578640 needs to be addressed, i.e. we need wayland target in mozilla test suite and be able to test builds on wayland and check for regressions there.

Comment 11

[Robert Mader [:rmader]]

Added a few bugs that IMHO we should fix before enabling Wayland by default as they are actual usability regressions compared to the X11 backend and not just "glitches".

Comment 12

[Val Packett]

Bug 1631023 also deserves to be added here. I personally hate the recently-used-order ctrl-tab but since people do use it, it shouldn't look broken. I might actually look into fixing it.

Comment 13

[Kan-Ru Chen [:kanru] (UTC+9)]

Not sure if bug 1707425 should be tracked here. I can only reproduce it under the wayland + proton tabs combination.

Comment 15

[Martin Stránský [:stransky] (ni? me)]

As Ubuntu is moving to Wayland (21.04 and perhaps later releases) and ships Firefox Wayland backend by default there this but is getting more important. We definitely need to test what is shipped to users.

Comment 16

[Hugo Osvaldo Barrera]

I opened a remotely related issue on this topic: #1720497

Basically, on systems where Xorg is not running but Wayland IS running, Firefox currently crashes out of the box. Firefox should fall back to Wayland is Xorg is absent, since crashing out-of-the-box is always the least desirable outcome.

Comment 17

[Martin Stránský [:stransky] (ni? me)]

(In reply to Hugo Osvaldo Barrera from comment #16)

I opened a remotely related issue on this topic: #1720497

Basically, on systems where Xorg is not running but Wayland IS running, Firefox currently crashes out of the box. Firefox should fall back to Wayland is Xorg is absent, since crashing out-of-the-box is always the least desirable outcome.

This is not what I mean here. Firefox still needs XWayland running even when Wayland backend is used and that's usual case in most Linux distros. Bug 1720497 is just a feature what needs to be addressed later.

Comment 18

[romulasry]

MOZ_ENABLE_WAYLAND=1 firefox is much faster on firefox 94.0.2 (64-bit)

Can't wait until this is enabled by default.

kde here on Fedora Rawhide (36).

Comment 19

[Darkspirit]

Done by bug 1749174 to test in Nightly what is already enabled by default in downstream Stable builds.