All PWAs in the same profile are merged with the first PWA that was opened (Linux-only)
See original GitHub issueDescription
All PWAs are merged with the first PWA that was opened. This only applies to Linux.
When some PWA is already running, all newly launched PWAs will merge with it and remain merged until all of them are closed. This will cause the app menu to display all PWAs as part of the first PWA that was launched, with its icon and desktop actions (if any).
Users can prevent this by installing each PWA into a different profile.
Steps to Reproduce
- Install at least two different PWAs into the same profile.
- Launch the first PWA.
- See that it has the correct icon.
- Launch another PWA without closing the first one.
- See that is merged with the first one and has the wrong icon.
Possible Solution
This cannot be fixed easily. The native part of the project currently launches Firefox with the --class
argument, which should set the WM_CLASS
property of the window to the PWA ID. However, because all Firefox processes in the same profile are connected together, all windows have WM_CLASS of the first PWA. Fixing this would probably require modifying Firefox C++ code. Check this comment and related discussions for ideas and possible solutions to fix this.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:6
- Comments:9 (4 by maintainers)
Top GitHub Comments
Hi,
This is how it works for me « manually » ie. not « true » PWA.
Regular Firefox has its legacy launcher :
Deezer has its own :
and Google Drive another one :
Firefox profile contains :
and profiles.ini contains :
In launchers, mind the Exec and StartupWMClass entries :
In profiles.ini, mind the naming of each Firefox profile, the same wording for each matters.
If placed into
~/.local/share/applications
the desktop files make those websites appear in the « app menu » as « regular » app’s.All these give me for years visually « separate » instances of Firefox for some websites I prefer to keep aside the main Firefox.
Ubuntu here, can’t say about Windows nor Mac, sorry.
xprop
can externally set the WM_CLASS of the window after it was created w/o modifying the Firefox binary itself. idk what this will do if you have wayland though.