Skip to content
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

Window class on Linux makes it impossible to use docks/launchers #1351

Closed
Slater91 opened this issue Jan 12, 2020 · 1 comment
Closed

Window class on Linux makes it impossible to use docks/launchers #1351

Slater91 opened this issue Jan 12, 2020 · 1 comment
Labels

Comments

@Slater91
Copy link

After the 2020.01 update, both Waterfox Classic and Waterfox Current identify themselves as "waterfox", so window class-based detection methods (e.g. the one used by Latte Dock) fail.

To Reproduce

  1. Open Waterfox Current and Waterfox Classic on KDE Plasma
  2. Both are identified and treated as Waterfox Classic on Latte Dock
  3. Right-click on the titlebar and select "configure special application settings"
  4. Both Classic and Current are identified as "waterfox"

Expected behavior
The two browsers should identify themselves correctly as "waterfox current" and "waterfox classic" as they did in the previous version.

My configuration

  • OS: Linux - KDE neon
  • Version: Classic + Current 2020.01
@Slater91 Slater91 added the bug label Jan 12, 2020
@Slater91
Copy link
Author

Note: it seems like something has changed between the 2019.12 version and the 2020.01 version. By setting "StartupWMClass=WaterfoxClassic" in the .desktop file, the issue goes away. This was not necessary in the previous version, so it seems like some change was made that impacts the ability of WMs to correctly identify the windows.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants