Closed Bug 1543600 (wayland-nightly) Opened 5 years ago Closed 2 years ago

[meta] Enable Wayland by default on nighly & qualified systems

Categories

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

Desktop
Linux
task

Tracking

()

RESOLVED FIXED
Tracking Status
firefox98 --- fixed

People

(Reporter: stransky, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: meta)

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

Depends on: 1534089
Type: defect → task

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.

(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.

Priority: -- → P3
Depends on: 1532618

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?

(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.

Depends on: 1519434

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

Depends on: 1548475
No longer depends on: 1519434

(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.

(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.

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
Blocks: 1635186

(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.

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

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.

No longer depends on: 1490297
No longer blocks: 1635186
Depends on: 1652783
Blocks: 1631462
Blocks: 1665817
See Also: → 1373752

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".

Alias: linux-wayland-nightly
Depends on: 1621660, 1650611, 1580595

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.

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

No longer depends on: 1650611
Alias: linux-wayland-nightly → wayland-nightly
Depends on: 1703073
Depends on: 1705048
Depends on: 1673000
Depends on: 1651347
Depends on: 1634096
Depends on: 1704175
See Also: 1373752
Depends on: 1507817
Depends on: 1711465
Depends on: 1661516
No longer depends on: 1711465
No longer depends on: 1651347
No longer depends on: 1507817
Depends on: 1709254
Depends on: 1721036

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.

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.

(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.

No longer depends on: 1704175
No longer depends on: 1634096
Depends on: 1577589
No longer depends on: 1577589
Depends on: 1726923

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).

Depends on: 1749174
Depends on: 1752101

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

Status: NEW → RESOLVED
Closed: 2 years ago
OS: Unspecified → Linux
Hardware: Unspecified → Desktop
Resolution: --- → FIXED
No longer depends on: 1752113
No longer depends on: 1709254
Blocks: wayland
Severity: normal → --
No longer depends on: wayland
Blocks: wayland-tests
No longer blocks: 1631462
Depends on: 1631462
No longer depends on: wayland-tests
Keywords: meta
Summary: [Wayland] Enable by default on nighly & qualified systems → [meta] Enable Wayland by default on nighly & qualified systems
No longer blocks: wayland-tests
Depends on: 1874717
No longer depends on: 1874717
You need to log in before you can comment on or make changes to this bug.