Forum Widgets
Latest Discussions
Edge Color Limitations for Workspaces
Earlier today, I installed the latest Edge updated and noticed that my color options for themes has been severely limited, with very poor choices. I am a heavy user of Workspaces in Edge and rely on colors to quickly identify each workspace that I use for different projects. Previously, I had a mixture of dark and light colors assigned to different workspaces that were a quick visual identifier. To get any sort of color separation, I now need to go with the light color theme to identify my workspaces. These colors are not as distinctive for me and the dark therme colors are so close together in the color palette, there is absolutely no distinction. Additionally, the new light theme even makes the tabs within the brwser harder to differentiate or distinguish. The tab icons are too softened and difficult to discern. While I don't mind suggestions or options for my personal settings, I do not appreciate being artificially limited to what the Microsoft design team has determined to be aesthetically pleasing. This should be a matter of choice. No one is a better expert on what works best for me than myself. Lately, I'm noticing in multiple Microsoft applications, visual design changes are being made arbitraily that negatively impact my daily workflow, with no added benefit.
Edge beta crashes after 5 seconds on some old versions of Windows 10
We have problems with Edge Beta versions 151.0.4129.15, 151.0.4129.21 and 151.0.4129.35. On launch Microsoft Edge briefly opens and then closes (like in 5 seconds) on Windows 10 RS1/RS2/RS3. I can't reproduce problem on other versions of Windows 10, such as TH1 or RS4
Webview2 exe missing after edge update
After the recent edge update, the webview2 exe is not updated together. C:\Program Files (x86)\Microsoft\Edge\Application\151.0.4129.59\msedgewebview2.exe is missing. This breaks webview2 apps on Windows. Is there some change to location of webview2? Any new API to get the location of the new webview2, or this is a genuine bug that need to be resolved by Microsoft?
The official place to report bugs
I am a user of the beta version of Edge on Linux. From time to time, I encounter bugs that I’d like to report. After some searching, this forum is the closest I have found to a bug tracker. So I was wondering whether there’s a dedicated place for reporting bugs or should I just post here?
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.Enhanced Security hinders performance of WASM applications (Including Blazor)
Hi, is there any official advice on what to do about "enhanced security" absolutely nuking performance of WASM? https://github.com/dotnet/aspnetcore/issues/48754 https://github.com/dotnet/aspnetcore/issues/56806 These existing tickets that were closed on the AspNetCore side, and it's been many years it seems and this is still an issue? I've submitted feedback through edge on this before but I have no way of knowing if this has been answered/looked at. We have a user who's required to have it on by policy and can't add it to the whitelist, and it's causing a pretty severe performance degradation. It just seems odd to me that the same company can produce two tools, and one of them absolutely breaks the other with seemingly no way to manage the downside at all.Seriously...? WHY is the "OPEN FAVORITES in NEW TAB" Setting gone again...???
This is getting absolutely rediculous.... Comes and goes willy nilly.... I stopped using the "workaround" script in the Shortcut Link, thinking you guys finally got your act together, but you didn't, so now I have to hunt that down and hope it still works. (BTW it does...) Right Click the Edge "Shortcut", click Properties, add the below to the End of the "Target" field, with a space between the text there and this. That's what I've done, works for me. The setting is back. "--enable-features=msFavoritesOpenInNewTabSetting" Further, why the heck is that Setting STILL not on my WORK Edge install? I mean, that's where I MOST need it, so I don't accidentally overwrite a page I'm working on. The level of incompetence with this company astounds me, a simple setting as this they can't keep working or add. Don't get me Started about Windows 11, the worst Start Menu they've ever created, completely UNUSABLE for us Power Users, you could have at least included it in Windows PRO, same for the proper Explorer Menu Bar, missing things with Taskbar, etc. NEVER going to Windows 11 until you fix all this... A person shouldn't be FORCED to use 3rd Party Applications in order to FIX the things we most work with, for them to work properly. I have literally over 100 Apps in my Start Menu all organized, grouped, labeled, and sized how I like. Win11 is literally UNUSABLE for me.Dutch grammar option disabled in Edge Writing Assistance
I am testing Microsoft Edge Writing Assistance with Microsoft Editor enabled. On both a clean unmanaged Windows 11 device and a managed Windows 11 device, Dutch shows Enhanced spell check as available, but the Grammar toggle remains disabled. When hovering over the Grammar toggle, Edge shows a not-allowed icon. This does not seem to be caused by enterprise policy, because the same behavior happens on a clean device without corporate policies. Dutch is listed by Microsoft as supporting spell check, grammar check and writing refinements in Microsoft Editor. Can someone confirm whether Dutch grammar is currently supported in the built-in Edge Writing Assistance experience? If it is supported, is there an additional Edge setting, policy, account requirement or language component needed to enable the Dutch Grammar toggle? Thanks.
