Bug 454600

Summary: PWA on wayland don't get their own window icon in the taskbar
Product: [Plasma] kwin Reporter: Magnus Jørgensen <magnusmj>
Component: wayland-genericAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: jorge_barroso_11, kbkozlev, markovs.i.mail, nicolas.fella, sebastien.leon, tnizametdinov
Priority: NOR    
Version: 5.24.5   
Target Milestone: ---   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Magnus Jørgensen 2022-05-30 09:30:45 UTC 
SUMMARY
Progressive web app integration with wayland is not working correctly.

STEPS TO REPRODUCE
1. Install a Browser that supports own window (no browser menus) window progressive web apps (PWA). Chromium-Browser, Brave-Browser, Google-Chrome, Microsoft-Edge. 
2. Open a web page that has support for running as a Progressive web app. Say Spotify or SoundCloud.
3. Add the PWA launcher to the OS using the browsers method for this. Most Chromium based browsers have this feature called "add shortcut" in the "more tools" sub menu. When clicking it you must  check the open as window shortcut. 
4. Now you launcher menu should have an icon/launcher that can start the PWA as an web application in its own  window. Attach this launcher to the taskbar 


OBSERVED RESULT
On kwin X11 this window will tie it self to the launcher of the PWA in the taskbar.
On kwin wayland this window will tie itself to the browser launcher in the taskbar. 

EXPECTED RESULT
On kwin wayland this window should tie it self to the launcher of the PWA in the taskbar.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
KDE Neon Stable
KDE Plasma Version: 5.24.5
KDE Frameworks Version:  5.94.0
Qt Version: 5.15.4

ADDITIONAL INFORMATION
Similar to 358277 but this is only in wayland. X11 works fine.
Comment 1 Nicolas Fella 2022-05-30 12:50:15 UTC 

*** This bug has been marked as a duplicate of bug 447845 ***
Comment 2 Nicolas Fella 2022-05-30 12:50:38 UTC 
This will be fixed in Plasma 5.25
Comment 3 Komorebi 2022-07-10 21:30:25 UTC 
Well, I'm using 5.25.2 and the issue still persists.
Comment 4 tnizametdinov 2022-11-10 09:33:28 UTC 
I'm on Plasma 5.25.5, but the issue is still there.
Comment 5 sebastien.leon 2022-12-19 13:36:11 UTC 
(In reply to tnizametdinov from comment #4)
> I'm on Plasma 5.25.5, but the issue is still there.

Have you try to set chrome://flags/#ozone-platform-hint to "wayland" ?
Comment 6 tnizametdinov 2022-12-19 14:20:55 UTC 
I already switched to X11.
Comment 7 tnizametdinov 2022-12-19 14:24:28 UTC 
But thanks for the hint!
Comment 8 Jorge 2022-12-20 22:28:14 UTC 
(In reply to sebastien.leon from comment #5)
> (In reply to tnizametdinov from comment #4)
> > I'm on Plasma 5.25.5, but the issue is still there.
> 
> Have you try to set chrome://flags/#ozone-platform-hint to "wayland" ?

This fixed it for me, quite similar in brave: setting brave://flags/#ozone-platform-hint to "Auto" or "Wayland". It comes configured with "Default" which at this point in time equals "X11"
Comment 9 Kaloian Kozlev 2025-01-23 08:48:55 UTC 
(In reply to Jorge from comment #8)
> (In reply to sebastien.leon from comment #5)
> > (In reply to tnizametdinov from comment #4)
> > > I'm on Plasma 5.25.5, but the issue is still there.
> > 
> > Have you try to set chrome://flags/#ozone-platform-hint to "wayland" ?
> 
> This fixed it for me, quite similar in brave: setting
> brave://flags/#ozone-platform-hint to "Auto" or "Wayland". It comes
> configured with "Default" which at this point in time equals "X11"

This fixed it for me also, thank you!