Forum Widgets
Latest Discussions
Angular Service Workers are not working properly after recent Edge update
Hello! I have an Angular application and I am using Service Workers for caching. Unfortunately after updating to the latest Microsoft Edge version (143.0.3650.66), many users were unable to load the applicaiton, because the cache in their browsers somehow became corrupted and the Service Worker did not recognized this and did not reloaded the page. Pressing CTRL+F5 or using incognito mode solved the issue, but it is not an acceptable solution for this app. Is this a known issue? Is there any known solution?
Marketplace offers for consulting services
We have several consulting service offerings live in the Microsoft Marketplace that are listed as "Software As a Service" offerings. It is recommended to list consulting services as a "Professional Service," but once an offer is live, you cannot change the offer type. So in order to classify these correctly, we'd have to recreate each service offering as a Pro Service offering and put it through the marketplace validation process again. I'm wondering what the benefit is to having marketplace service offerings listed as "Professional Service" vs. "Software As a Service?" We're trying to decide if it's worth the effort to recreate these offers as Pro Service offer types..
New Tab search UI (Ctrl + Shift + A) has changed - how to revert to previous behavior ?
Since the latest Microsoft Edge update, the Tab Search panel opened with Ctrl + Shift + A has changed. It now opens on the side instead of the center, and arrow key navigation no longer works. Only Tab navigation works now. this makes it much harder to use quickly. Is there any way to restore the previous centered Tab Search UI, or re-enable up and down arrow navigation, or undo this specific UI change ? The old version worked perfectly for my workflow. The new version slows everything down. Thanks MichaelPlease, bring back the "Microsoft Edge rounded corners" option
Hello As of today, the "Microsoft Edge rounded corners" flag in edge://flags/ no longer works (the option is disabled to revert to the old appearance). Since Microsoft no longer gives users a choice in appearance, they're trying to force us to switch browsers... ?? No more option to hide the Extensions button in the toolbar, a display bug for over a month regarding the color of the buttons in the title bar (black instead of white like in Windows), etc... Please MS, bring back this option And is there an "flag" (to add to the shortcut, for example) to restore the old appearance ? Thanks
Fresh install, forgot recently changed passwords
Ive locked myself out of my accounts linked to prettey much all. The account recovery page isnt very helpful, already failed 2 requests, tried phoning to speak to an actual person, some AI gave me the web address i had just used and now hangs up on me with no option to speak to anyone real. Can anyone from microsoft help me with this? Frankly the AI you guys are using atm is terrible, i need to speak with a real person so i can actually verify and get my accounts back.
Microsoft Edge - Window Titlebar single click issue
On Linux systems running Wayland, Microsoft Edge Stable exhibits incorrect titlebar click behaviour. When the window is maximized, a single left-click on the titlebar incorrectly triggers a restore-to-windowed-state action. When Edge is in a normal (non-maximized) state, single-clicking the titlebar causes unintended small positional movements , as if a drag or snap gesture were initiated. This behaviour does not occur in Firefox, nor did it occur in older Edge releases . It appears specifically when Edge is using Chromium’s client-side window decorations under Wayland. Attempts to configure Edge to use system (server-side) titlebars — including the UI toggle (“Use system title bars and borders”), launcher flags (`--force-system-title-bar`, `--gtk-version`, `--enable-features=WaylandWindowDecorations`) and `.desktop` override configuration — do not resolve the issue. This suggests a hit-test / event-targeting regression in the Chromium Wayland + CSD (client-side decoration) path. Additional Notes This matches the known open Chromium issue regarding misaligned hit-test regions in GTK4 CSD under Wayland . Since Edge now defaults to GTK4, the incorrect click detection is being triggered before compositor-level decoration logic applies. Firefox, which uses server-side GNOME decorations under Wayland, does not exhibit this behavior.
