Forum Widgets
Latest Discussions
android links
I use edge on my desktop and would like to use it on my android phone. I use Opera on my android because it allows me to save a website link to the home screen with the correct icon for that page. If I try to do the same thing with edge it simply produces a plain icon with a single character (probably the first letter of the link), which means there are several such links all with the same character, which are indistinguishable from each other. Is there a workaround?
Edge MV2 Deprecation Timeline?
Chrome has laid out a timeline for deprecation of Manifest V2 (https://developer.chrome.com/docs/extensions/develop/migrate/mv2-deprecation-timeline) and it's mentioned that MV2 extensions will stop working gradually post June-2024. I couldn't find any update regarding Edge. Will the same timeline be applicable to Edge too or will there be a different timeline that Edge targets? The last article regarding Edge MV3 timelines I was able to find was here: https://learn.microsoft.com/en-us/microsoft-edge/extensions-chromium/developer-guide/manifest-v3 but that seems outdated.Edge Workspaces gone missing
Hi there! I'm a bit lost here, would appreciate if you guys can help me out. So today I logged in to my computer and went to Edge, as usual, but to my surprise, ALL my workspaces are simply gone, there is no sign of any of them. I was hopping I could find them somewhere on my sharepoint or onedrive, and I'm becoming a little bit desperate of losing it all...
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?
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 RS4The 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.
