Starting Edge as a process immediately fires exited event
Hi! Recently I have encountered a rather annoying bug on Windows 11 IoT LTSC where I launch an edge as a process from my .net 9.0 C# code. I need to track Edge and if it exits for some reason I have to relaunch it. I'm tracking whether it has exited by subscribing to the Process.Exited event, but on the beforementioned operating system this event immediately fires even though the Edge itself visibly does not close and stays functional without any problem. This results in infinite edge processes getting launched, since every new instance also exits. Interestingly this issue does not occur when tested with other browsers nor it occurs on Windows 11 Pro, everything works completely fine in these two scenarios. I'm guessing IoT version has some kind of different power plan to reduce battery drainage and CPU usage if possible. My other assumption is that the msedge.exe available with default windows is just a parent process on the IoT version, and it just starts the actual processes needed to present the content of my web app. It'd be great if you could check this and come back to me. Thank you! Kind regards, Gallusz.Microsoft Editor does not work
As the title states, if you have the Microsoft Editor enabled in Edge (this appears to be any version from Stable to even Canary), no spell or grammar check will work at all. If you enable the standard editor, you will get at least spell check back. This screenshot is with the MS Editor enabled - it seems to know what is spelled incorrectly but gives you zero suggestions. And here is the standard spell check working as it should. Testing in Edge stable 136.0.3240.50 + Dev 137.0.3282.1Sending page from other device (e.g. Edge on Windows 11) to Edge Android is working
Hi, I think I found a bug in Android Edge Enterprise Sync that affects all AAD account. Chromium-based browser has a "push"-like mechanism to handle sending a tab across session. This feature works when "Notifications Enabled" under edge://sync-internals has the status of True. (Semi-related old bug on the upstream: https://bugs.chromium.org/p/chromium/issues/detail?id=42145) When it is inactive (status False) pages you sent to target device will not trigger any notification (user click on the notification to open the sent URL); you have to go to settings to initiate sync to make the notification appears. I tested three different AAD account from different tenants and found out that "Notification Enabled" is always false when signed-in to Edge Android. Further triaging suggests that this bug: Only affects AAD account. MSA account has "Notification Enabled" = true. Only affects Edge Android. Windows and Linux Edge has "Notification Enabled" = true Happens on Edge Android stable (100.0.1185.50) and Play Store Beta/Insider (102.0.1245.12). When "Notification Enabled" = true I get the sent page/tab within few seconds, which is great. Sadly this never happens with Edge Android + AAD account. I have tried to file bug report via in-app "send feedback" quite few while back, no response. More recently, I submitted a support ticket, but got brushed off as business support case and suggested to pay minimum to $95 just to report a bug, which is silly. So, I hope posting this will bring the attention to Edge Team. Kelly_Y 😉 Cheers, AryaFound a bug in Edge 87 policy
So whenever I enable this policy This option in Edge which is related to secure DNS lookups, becomes unavailable and disabled I see no relation between the 2 options. in Edge policy I only have this which should only apply to this and not other settings. so In my perspective this is a bug/unwanted behavior. I'll report it using feedback button on Edge too. Edge Dev 87-88 Windows 10 20H2 if for any reason this is actually an expected behavior, please let me know with some explanation, thank you.
