Open Bug 1694928 Opened 2 months ago Updated 13 days ago

[Wayland] WMClass inconsistent in Nightly

Categories

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

Firefox 87
defect

Tracking

()

UNCONFIRMED

People

(Reporter: grayshade, Unassigned)

References

(Blocks 1 open bug)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:87.0) Gecko/20100101 Firefox/87.0

Steps to reproduce:

This might be a dupe of another issue, but I can't find it right now and I think that one was a little confused, so sorry.

  1. run Firefox Nightly Wayland in GNOME
  2. check with lg the window class (firefox)
  3. run Firefox Nightly Xwayland in GNOME
  4. check the window class again (Nightly)

Actual results:

Nightly has different window classes depending on whether it's running on Wayland or not. This can be pretty annoying because a distro package (I'm using firefox-nightly-bin in Arch/AUR) might have a .desktop file with StartupWMClass=Nightly, which won't work on Wayland.

If the startup class is wrong, users might:

  • not get "running" notifications until some long timeout expires
  • not be able to add the browser to their DE app launcher like GNOME's dock
  • not be able to invoke window commands like "New private window"

Expected results:

WMClass should be the same regardless of whether it's running in Wayland or not.

Component: Untriaged → Widget: Gtk
Product: Firefox → Core
Blocks: wayland
Priority: -- → P3

Is there any reason why this bug is not fixed?

(In reply to Hideo Oshima from comment #1)

Is there any reason why this bug is not fixed?

Yes, because I just don't know how to fix that. Any help is welcome.

You need to log in before you can comment on or make changes to this bug.