Jan 28 2020 10:35 AM - edited Jan 28 2020 10:50 AM
Hello Insiders, today we’re releasing build 81.0.403.1 to the Dev Channel. One thing that we didn’t get a chance to mention last week was that we had to temporarily disable casting. It’s still functional, but you have to enable the edge://flags/#load-media-router-component-extension flag. We plan to enable it by default once again in a future update.
We also started a discussion here around two features that many of you have expressed that you miss from Edge Legacy: Set Aside Tabs and Warn On Close. Users of lots of tabs in particular will want to check out https://techcommunity.microsoft.com/t5/discussions/discussion-set-aside-tabs-and-warn-on-close/m-p/1....
Finally, we made a new blog post about a very cool web developer feature: 3D view. You can learn how to enable it and check it out for yourself here: https://blogs.windows.com/msedgedev/2020/01/23/debug-z-index-3d-view-edge-devtools/. As for our most noteworthy changes this week:
Added features:
Improved reliability:
Changed behavior:
Known issues:
As always, thanks for all your feedback and suggestions, we couldn’t do it without you!
Jan 30 2020 08:11 AM
I'm seeing an issue on the most recent DEV Channel build that doesn't show up in the GA build. If I attempt to import settings from either IE or Chrome, the browser immediately crashes, regardless if the other browser is open. This occurs regardless of whether I'm signed into a profile or not. I have been able to reproduce this on multiple machines.
Jan 30 2020 08:47 AM - edited Jan 30 2020 08:48 AM
Hello,
I have a couple of issues and both have to do with components ( edge://components/ )...
First, there appears to be a regression where edge://components/ is no longer displayed in dark mode/dark theme if you have that selected.
Secondly, "Check for update" does not work. For example: CRLSet has been on Version: 5649 for many days now and it is updated twice daily (so it is quite a few versions out of date).
Jan 30 2020 10:05 AM
Users of certain security software packages will see all tabs fail to load with the error STATUS_ACCESS_VIOLATION. The only way to prevent this behavior is to uninstall that software.
Not a SINGLE tab is loading... Even settings... Please see the screenshot..
Tried to reinstall edge, cleaned all sorts of caches and user profiles folders... No luck...
Any software that I should remove? What is this software?
Any help on getting this fixed is greatly appreciated!
Jan 30 2020 10:23 AM
@elastep and yes, I've tried --no-sandbox and --disable-features=RendererCodeIntegrity
switches with no luck.
And I do not have Symantec installed...
Jan 30 2020 12:44 PM
@elastep wrote:Users of certain security software packages will see all tabs fail to load with the error STATUS_ACCESS_VIOLATION. The only way to prevent this behavior is to uninstall that software.
Not a SINGLE tab is loading... Even settings... Please see the screenshot..
Tried to reinstall edge, cleaned all sorts of caches and user profiles folders... No luck...
Any software that I should remove? What is this software?
Any help on getting this fixed is greatly appreciated!
Forcepoint (websense)
Jan 30 2020 12:48 PM
@HotCakeX Yes... Shoot... Thanks for the help.
Jan 30 2020 02:36 PM
@Jeffrey Thorpe @elastep for anybody running into the STATUS_ACCESS_VIOLATION issues with Forcepoint, we're actively engaging with them about this issue. They can reproduce it themselves, but they don't have a fix for it yet (nor do we), and we're also looking into engaging Google since this is likely something we inherited from upstream Chromium.
Jan 30 2020 03:00 PM
If I attempt to import settings from either IE or Chrome, the browser immediately crashes
@SixStringFlyboy I believe this is an issue that was fixed in today's Canary (which means it should be in the next Dev build). You could download Canary and try it if you want to confirm.
Jan 30 2020 03:02 PM
I have a couple of issues and both have to do with components ( edge://components/ )...
@puff-m-d I'll let the owner know, thanks for reporting!
Jan 30 2020 07:10 PM
Jan 31 2020 11:25 AM - edited Jan 31 2020 11:27 AM
I'm also noticing intermittent text corruption in the 81.0.403.1 build on my system with Intel UHD 620 integrated graphics.
Jan 31 2020 11:41 AM
Feb 01 2020 10:11 AM - edited Feb 01 2020 10:13 AM
Hello,
The second issue that I posted about in my above post ( https://techcommunity.microsoft.com/t5/discussions/dev-channel-update-to-81-0-403-1-is-live/m-p/1140... ), ""Check for update" does not work.", now appears to be fixed.
Feb 01 2020 04:43 PM - edited Feb 01 2020 04:54 PM
@jbart007, @josh_bodner and @Heath Bates
I'm also encountering text rendering issues like you'd described occurring when selecting text after updating to Edge v81.0.403.1 and also installing KB4528760 and KB4532938 for Win10, like seen in the below screenshot:
I've provided some additional details (as well as referenced your comments) in my attempts to narrow down under what circumstances this occurs in a new thread:
Bug: Selecting Text Causing Other Lines to Render as Random Characters (in Edge v81.0.403.1)
Hopefully, that new thread will at least help save time for others encountering the issue and considering submitting bug reports regarding it or provide some more details to help narrow down and fix the issue.
The issue remains in some cases even after deselecting text, and appears intermittent, as I'd detailed in that thread. Alt-tabbing and other cases where rendering/repaint gets triggered again result in different random characters appearing each time.
Please feel free to chime in, in that thread, if have any further details to add.
Feb 02 2020 12:11 AM
Feb 05 2020 03:47 PM
@HotCakeX thanks for the update. I'm glad to hear a fix is in the pipeline for release to Edge Dev channel. Edge Dev just updated now, so hopefully don't end up seeing the issue in it. Will reply if reoccurs.
Feb 05 2020 06:06 PM
@HotCakeXUnfortunately, the major update for Dev channel just out today (81.0.410.1) failed to fix the text rendering issues occurring after text selection.
You can see the issue remains in the below screenshot (eg. occurring on this page) with random characters under "Pay as you go" above the selected text, which appears as different random symbols every time re-rendering occurs (eg. Alt-Tab and back).
Also, the issue remains even after deselecting text, as shown in the below screenshot, even after Alt-Tab or otherwise causing it be re-rendered again:
Feb 05 2020 07:14 PM
Yes,
"the visual glitch is completely random and not caused by any user actions, although highlighting the text should fix it (at least until it happens again). It's caused by an upstream Chromium bug, and we received the fix for it from them earlier this week, so it should make it into the next Dev release."
Feb 06 2020 05:14 AM
@josh_bodner Is sync of Search Engines on the roadmap? Or will the be included as part of the the general "Settings" sync toggle?