[Wayland] PWAs no longer appear as separate app windows — all group under main Edge icon
Hi, Since around 2025-09-07 to 2025-09-10, I’ve noticed that on GNOME (Wayland) all installed PWAs (even across different profiles) now appear grouped under the main Edge browser icon in the GNOME Shell dash/taskbar. Previously, each PWA would open in its own window group with its own icon. This is still the behavior in Chromium/Brave/Chrome, and can be restored there by editing the PWA’s .desktop file to set: StartupWMClass=<same value as Icon> However, Edge now seems to ignore StartupWMClass completely on Wayland, breaking workspace separation and making task switching hard. Environment: Ubuntu 25.04 GNOME 48.0 / Mutter (Wayland) Kernel 6.14.0-29 Intel Iris Xe GPU Edge (latest stable, observed post 2025-09-13) Repro steps: Install any PWA (e.g. Outlook, Teams, Spotify) from Edge Launch it (from any profile) Observe that it appears grouped under the main Edge browser icon Expected: PWA shows under its own icon and window group like in Chromium-based browsers Actual: All PWAs are bundled into the main Edge window group Editing StartupWMClass in the .desktop file no longer helps This regression makes PWAs much harder to manage on Wayland. Please route to the Linux/Wayland team if possible. Thanks!PWA shortcuts don't keep asociated with window - Linux
I recently upgraded to version140.0.3485.14 (Official build) beta (64-bit) and noticed that my PWA, even if they open correctly in a independent window, don't show the "running window counter" on the taskbar. So, for example, if a open Outlook, the window open and loads the app, but if a I click the icon again, it opens another window, wich is a little annoying. I tried removing the PWA from Edge, rebooting, and installing again, but didn't work. Because the only change I made is updating Edge, I think is related to this build. (too lazy to go back or install the stable release)Make Share function in Edge more useful
posting from latest available Edge Version 82.0.418.0 (Official build) canary (64-bit) the Share looks like this so it expects user to have the UWP apps installed. there are problems with that: UWP is not available on all platforms. on Windows 8.1, on Mac, and soon on Linux. also some popular apps like Instagram, their UWP version haven't been updated in ages. Facebook app is also old. also my installed app list in Edge (PWAs) look like this: You see, I've added my favorite social network websites as apps in Edge, PWAs are better, they do not require installation and experience is the same in all platforms. so now when I want to share something on Twitter, Facebook, Reddit etc, I have to use the method that I've been using since 15 years ago. the old copy paste method. because the Share functionality is totally useless at the current state. my suggestion: make Share functionality in Edge to detect the installed PWA apps, websites added as an app, and then offer them on the Share window as options. when I have Twitter added as PWA in Edge, I obviously don't want it double on my system by installing the UWP version. the same applies to the rest of the social networks.Add the option to open favorite items in installed Edge apps
to clarify what I'm referring to: I have YouTube website installed as an app in Edge browser when I go to YouTube.com from main Edge window (Not the pinned website or PWA), and right-click on a link, I get this option which lets me open the link (in this case it's a video), in the pinned YouTube app. but when I right-click on the YouTube favorite item in the favorite bar, I don't see this option. it's missing from there. it makes sense to add the same option in favorite items right-click menu too. This is Version 82.0.449.0 (Official build) canary (64-bit) the nature of this bug prevents me to properly send it using feedback button on Edge browser, so I really hope someone from Microsoft will take this manually and let the team know about it. thank youLove the new optional tab strip for PWAs
Edge Version 88.0.692.0 (Official build) dev (64-bit) the flag for this new feature is: edge://flags/#enable-desktop-pwas-tab-strip you will be asked if you want tab strip for your PWA upon installation These are the kind of prompts you receive if the website offers the install option on the address bar. if a website does not offer the install option in the address bar, and you try to install it using: (ellipsis menu => Apps => install this site as an app) then the prompt will look like this, a 3rd option will be offered.Notification badges for PWAs pinned to the taskbar
If possible, it would be good to see notification badges on taskbar for the pinned website like Twitter and other social media platforms we already get some sort of hint when there is notification available on Twitter on Edge favorites toolbar, (using Edge canary 83 at the moment) notice the small red dot. it disappears when I go to Twitter and check my notifications or mark them as read. i think this is great and needs to be visible on the Taskbar pinned items too.[Feature request] Web Apps (PWA) - Option to enable/ disable extensions per app
Edge web apps are great, and I like that Edge Extensions is used inside the apps. One feature request that would further improve this though, would be to make us able to enable/ disable extensions per installed web app. For instance, I want dark mode from Dark Reader in some apps, but in other apps I don't want that. Well, bad example, Dark Reader has a user maintained list of domains to either dark mode or not dark mode. But you get the point.New Feature in Edge Canary Version 84.0.492.0 - install sites as share target for the whole Windows
This newly added flag: Enable Share Targets Enables installed web apps to register for and receive Share requests from the Windows shell. Requires the Web App Identity Proxy functionality to be enabled as well. – Windows #edge-share-target which requires this flag to be enabled as well: Web Apps Identity Proxy Enables installed web apps to be created with modern Windows application identity for better integration with the Windows shell. – Windows #edge-webapp-identity-proxy the description of the flag is self explanatory but what it does is that when you install a social network website such as Twitter as an app in Edge, it will be added as a share target when you press Share button on Edge or anywhere on Windows 10. Twitter will be registered as a system-wide share target so any app or program in Windows 10 can share files to Twitter website. this was requested before and now implemented. thank you! this is an example of Share from Photos app and you see Twitter which is the website installed as app in Edge is a share target on the list. Keep in mind that this is the first implementation phase for this feature so it might have bugs or might not work for you at all.
Solution for PWAs not appearing as separate apps on Linux taskbars
Hi everyone, I recently Installed Microsoft Edge stable on Kubuntu Linux, and I ran into some problems using Progressive Web Applications (PWAs). Launch one Edge PWA (say, Microsoft Teams). It appears normally. Launch a second PWA (say, Microsoft Outlook). Both windows — and every PWA you launch afterward — collapse into a single taskbar group under the first PWA’s icon, identified as msedge. Pinned PWA launchers never show as running. Pinning a running PWA window produces a generic page icon that launches the bare Edge browser when clicked. Launching a PWA from the application menu briefly shows the launcher’s startup placeholder in the taskbar, which then disappears and is replaced by a separate, unassociated entry. This isn’t KDE-specific. GNOME users have also reported issues. After some troubleshooting with Claude, the issues were traced to a mismatch between how the PWAs are identified in the .desktop PWA launchers created by Edge and the app ids reported to Wayland, starting in September 2025, when Wayland was used by default. Identifier Value Example (Microsoft Outlook) Window app_id (native Wayland) msedge-_<appid>-Default msedge-_lkkahpbimdkjdjjiijflmhaeameegbcm-Default Desktop entry filename msedge-<appid>-Default msedge-lkkahpbimdkjdjjiijflmhaeameegbcm-Default StartupWMClass= in that file crx__<appid> crx__lkkahpbimdkjdjjiijflmhaeameegbcm So the solution is StartupWMClass in the .desktop launcher for the PWA to the Wayland app_id. I have a simple Bash script that will do this for all currently installed PWAs as a workaround, but the automod removed that post the last time I tried to post it. The suggested fix for Microsoft This should be a small change to Edge’s desktop-entry generation on Linux: write the Wayland app_id (msedge-_<appid>-<profile>) into StartupWMClass=, or better, make the window app_id match the desktop entry basename per the freedesktop convention. No compositor-side changes are needed — the verified workaround above demonstrates that. I’ve reported this through Edge’s in-browser feedback tool (Alt+Shift+I) with the full diagnosis. If you’re affected, sending your own feedback referencing the same details is the best way to get it prioritized — the in-browser channel is what reaches the Edge team’s triage.
