Web Apps aren't matched on GNOME when using native Wayland

[chrisawi]

This is also reported against the Chromium flatpak: flathub/org.chromium.Chromium#216

OS: Fedora 38 Silverblue (Wayland)

Using com.google.Chrome from Flathub with chrome://flags/#ozone-platform-hint set to Auto, web apps are matched as Google Chrome.

I checked in Looking Glass (Alt+F2: lg), and the wmclass is chrome-APPID-ProfileName rather than crx_APPID, which is the StartupWMClass (and is correct for the X11 WM_CLASS). I can make it work by changing StartupWMClass to match (conveniently, I can just copy the icon name), but that would almost certainly break matching under X11.

I suspect this same setup works with the Chrome RPM because GNOME also matches on the .desktop file name, which is chrome-APPID-ProfileName.desktop. I guess this is ultimately a Chromium bug, but I wanted to bring it up here because it's only broken in the flatpak.

[pobthebuilder]

I did some troubleshooting with this.

On my system Chrome is creating PWA with the following in the .desktop file (example for YouTube Music):
StartupWMClass=crx_cinhimbnkkaeohfgghhklpknlkffjgod

However, if I examine the windows themselves, at least under Wayland, the WMClass is:
chrome-cinhimbnkkaeohfgghhklpknlkffjgod-Default

Changing the StartupWMClass in the .desktop file to be correct:
StartupWMClass=chrome-cinhimbnkkaeohfgghhklpknlkffjgod-Default

(i.e. replace the crx_ prefix with chrome-; and add the -Default suffix)
Everything is working great. I need to do this for every PWA I install manually.

Does Chrome need to use a different WMClass in the .desktop file when using Wayland?