Feb 15 2022 10:54 AM - last edited on Feb 24 2022 11:47 AM by MissyQ
Hello Insiders! Today we’re releasing build 100.0.1163.1 to the Dev Channel. In the community this week, we were wondering if you were aware of our Youtube channel at https://www.youtube.com/channel/UCIGx7oT8p6-jUpOfg98yelA/videos. In case it’s been a while since you’ve been there, you may want to catch up on our latest videos, which showcase how to set up IE mode: https://www.youtube.com/watch?v=A2o0x9-0urE, and give an overview of what’s new for the F12 Dev Tools in Edge 97: https://www.youtube.com/watch?v=qbDLtE0a_yQ.
Also, in case you missed it last week, please consider taking our regularly-scheduled survey here to tell us how we’re doing in our engagement with you and how we can do better: https://go.microsoft.com/fwlink/?linkid=2187016. As for what’s new in the product this week:
As always, it’s your consistent feedback that keeps us going; we couldn’t do it without you!
Feb 15 2022 11:14 AM
Feb 15 2022 12:35 PM
Feb 15 2022 04:49 PM
Feb 15 2022 04:57 PM
Feb 16 2022 02:08 AM
Feb 16 2022 03:22 PM
Feb 16 2022 05:21 PM
Feb 16 2022 09:51 PM
@josh_bodner Good, this version again starts on my Linux box (Fedora 35 XFCE) without crashing. However, the default start page does not come up. Just keeps waiting in "New tab". Some messages printed to terminal if started with a command:
[2545:2545:0217/074009.176307:ERROR:sandbox_linux.cc(377)] InitializeSandbox() called with multiple threads in process gpu-process.
[2413:2413:0217/074034.058424:ERROR:network_service_instance_impl.cc(1001)] Network service crashed, restarting service.
[2413:2413:0217/074034.105534:ERROR:smartscreen_dns_resolver.cc(103)] SmartScreenDnsResolver::OnComplete Error: -2 DidTimeOut: 0 URL: https://ntp.msn.com/edge/ntp?locale=en-GB&title=New%20tab&dsp=1&sp=Bing&startpage=1&PC=U531
Opening the tech community page added:
2413:2413:0217/074621.582839:ERROR:interface_endpoint_client.cc(659)] Message 6 rejected by interface blink.mojom.WidgetHost
Feb 18 2022 02:28 PM
@rshupak from a technical standpoint, the fix is that when the mini menu is fully onscreen, keyboard stroke will no longer close it or be passed into it, but instead passed to the underlying webpage so it can handle it the way it normally would when text is highlighted.
Since you say that you're immediately hitting the keyboard shortcut, I suspect you're hitting it during that animation where the menu appears, and that the fix may not apply during that animation. If you don't immediately hit the keyboard but instead wait a little bit, is it any better?
Feb 18 2022 02:29 PM
@Tio_Dep We just published a new Canary build yesterday, is it any better? We've been tracking quite a few crashes in Canary and haven't been pushing new builds because of them, although obviously we already published a build with at least one crash.
Feb 18 2022 02:41 PM
Feb 18 2022 04:32 PM
@josh_bodner First, the menu also interferes with double and triple click. Assuming these work, Ctrl+C appears to work if I wait. I specifically waited until I saw the menu appears. Typically the menu will immediately disappear but sometimes it remains and disappears as soon as the control key down.
I want to stress that double click and triple click are seriously broken when the menu is not disabled. They work 100% when the menu is disabled.
Feb 18 2022 04:34 PM
Feb 19 2022 01:46 AM
Feb 19 2022 07:36 AM
Feb 21 2022 03:59 PM