[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!
Latest Stable Linux build of Edge crashes when I download something.
When I download something from the internet and When I click save as the browser crashes, using RPM linux build on Fedora and using the latest stable version at the time of writing this discussion version Version 143.0.3650.139 (Official build) (64-bit)
Video Super Resolution Missing Options in Setting
Enhance videos in Microsoft Edge (Flag: #edge-video-super-resolution) is missing critical options in setting, making it impossible to function properly. In Version 136.0.3240.29 (Official build) beta (64-bit), as well as the previous beta build, it is missing the option to choose from three methods of video enhancement, as shown in screenshot. Here is the setting from latest beta build: This is how it is supposed to look: Thus, beta build defaults to Microsoft Super Resolution and I can't find a way to use graphics driver enhancement like RTX Super Resolution, which is critical to my experience. Also, HDR is no longer supported when video enhancement is enabled, which I believe is a limitation of Microsoft Super Resolution.
MS Edge - Sidebar and copilot not working on Linux Ubuntu v24 LTS
Sidebar not syncing or accepting new app additions (+). Copilot button is dead/inactive. Sidebar settings are well configured. Using the latest version of the Ubuntu OS and MS Edge. Functionality appears to be absent as product was released without full functionality....Lame!
Bug: Empty bar at bottom of screen on Android 14 Honor 70 / MagicOS 8.0
After updating Microsoft Edge to version 142.0.3595.66 on Android 14 with MagicOS 8.0 on an Honor 70 smartphone, a permanent empty strip appears at the bottom of the screen when using gesture navigation. This issue was not present in previous versions, such as 141.0.3537.99. Disabling the "Edge-to-edge Everywhere" or "Edge-to-edge Tablet" flags does not resolve the problem. It seems to be related to the new edge-to-edge design introduced in the latest update. Please fix this issue or add an option to disable the bottom padding. Thank you.Mica issues again (title bar + context menus)
Weird bug again - in both Stable/Dev the title bar mica effects are not working, but the dropdown & context menu (three dot settings) is. In Canary, the title bar mica effect *is* working, but the dropdown/context menu is not (solid white). I reported via feedback as well. Canary: Dev/Stable:
Microsoft Edge PDF Reader - signature validation warning for official signatures
Since the last edge update we are running into the following issue, which triggers support tickets on our side. It seems that the edge internal PDF Reader now supports validation of digital PDF signatures. This new feature however is incomplete and causes a lot of confusion for edge users. "Official" signatures are labeled as "Unknown Signature" and "The validity of the signature is still unknown": "Official signatures" means qualified signatures from members of the EUTL - the European trust list as defined in ETSI TS 119 612 („Trusted Lists“): [...] the European Commission publishes a central list with links to the locations where the national trusted lists are published as notified by Member States. This central list, called the List Of Trusted Lists (LOTL), is available in both a human readable format and in a format suitable for automated (machine) processing XML. Parts of the edge PDF reader seems to come from *dobe itself which adds additional confusion since in their products (*dobe reader, acrobat etc) the signatures are correctly verified. They support this list for several years now (next to their own AATL list). I tried to find out whether this feature is 'work-in-progress' or it is a bug however the last published roadmap is quite old and doesn't give helpful information regarding this aspect. So my question is: Is full support of PDF signature validation including support of the EUTL planned and if so when?Edge Pdf Viewer does not support page=Fit (only FitV or FitH works)
Dear community, I found that the Edge Pdf Viewer does not allow to display a pdf so that its first page fully fits into the window (no part of the PDF is out of the viewport). You can use the following URL to verify: https://creativelab.berkeley.edu/wp-content/uploads/2019/12/1920X1080-HORIZONTAL-template.pdf#page=1&view=Fit Test Case 1 When the window width gets too small, the window will display a horizontal scrollbar instead of scaling the pdf to fit the width: Test Case 2 When the window height gets too small, the window will display a vertical scrollbar instead of scaling the pdf to fit the height: When I use either FitV or FitH, the respective behaviour is as expected. But I need to combine both behaviours, and thus Fit would be the right option, which seems to be ignored by Edge. When I test the same parameters in other Browsers that use a Chromium engine, it works. Microsoft Edge Version 141.0.3537.85 (Official Build) (64-Bit) Windows 11 Thanks for any advice and thoughts! If there is a dedicated place to create a bug report, please let me know.
