-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PWAs and shortcuts are associated with the main browser window #39
Comments
Investigating closer, StartupWMClass seems to be missing from the main com.google.Chrome.desktop file, compared to the "regular" package: However, adding this to the desktop file doesn't actually fix the problem either way. Icons seem to have fixed themselves during the day somehow though. |
I have this issue too. |
refi64
referenced
this issue
in refi64/flextop
Apr 7, 2021
Otherwise, GNOME Shell won't match its StartupWMClass, so the applications won't appear separately from the Flatpak app in the dock. This also includes a system for migrating the affected desktop files automatically. Ref. flathub/org.chromium.Chromium#83 and flathub/com.google.Chrome#10
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi!
After granting chrome access to ~/.local/share/applications and ~/.local/share/icons, adding shortcuts to PWAs and other websites they are still associated with the launcher to chrome, meaning they are all grouped under the main window:
Checking the WM_CLASSes, they seem to be the set correctly compared to the "regular" version of chrome and are the same for both:
Browser:
WM_CLASS(STRING) = "google-chrome", "Google-chrome"
YouTube PWA:
WM_CLASS(STRING) = "crx_agimnkijcaahngcdmfeangaknmldooml", "Google-chrome"
Comparing the desktop files, nothing really stands out.
Flatpak:
Regular chrome:
The icons also doesn't show up properly in the launcher:
The text was updated successfully, but these errors were encountered: