Dev channel update to 80.0.334.2 is live

Microsoft

UPDATE 2:  We published 334.4 today to more broadly disable favorites sync, which should fix some sync-related crashes that users have been experiencing.  

 

UPDATE:  We published 334.3 today to fix an issue where navigation on some websites was taking an extraordinarily long time for some users.  We're also hoping to publish another small revision next week to fix a couple of known crashes.  

 

Hello insiders, today we’re releasing build 80.0.334.2 to the Dev channel!  The most important thing to know this week is that, after last week’s sync issues, we’ve temporarily disabled favorites sync to prevent any more duplication.  As for the other noteworthy changes: 

 

Added features: 

 

  • Added a right-click option to sort individual favorites folders by name from the Favorites management page.
  • Added a new setting to always use Strict Tracking Prevention inside InPrivate windows.

 

Improved reliability: 

 

  • Fixed a crash on launch.
  • Fixed an issue where searching from the address bar sometimes crashes the browser.
  • Fixed a SmartScreen crash when downloading certain items.
  • Fixed an issue where selecting context menu items on certain favorites entries causes a browser crash.
  • Fixed an issue where renaming a Collection sometimes crashes the Collections pane.
  • Fixed an issue where Application Guard windows sometimes crash upon startup.
  • Fixed an issue where navigation fails in Application Guard windows.
  • Fixed an issue where closing tabs that contain websites that are blocked by SmartScreen sometimes causes a browser crash.
  • Fixed an issue where deleted or edited favorites aren’t synced properly, causing the edit to be undone when it syncs back down.
  • Fixed an issue where syncing gets stuck in the “Setting up sync” state on browser startup.
  • Fixed an issue where processes that grow too large and stop working aren’t automatically fixed.
  • Fixed an issue where sync sometimes fails after restoring tabs after a browser crash.
  • Fixed an issue where large Collections aren’t properly exported to Word.
  • Fixed an issue where exporting a Collection to Excel sometimes fails.
  • Reduced the number of times a user needs to sign out and sign back into the browser in order to fix sync.

 

Changed behavior: 

 

  • Temporarily disabled the ability to export Collections to Word and Excel on Mac.
  • Temporarily disabled one form of DRM support on ARM64, which may impact the ability to play certain DRM-protected videos.
  • Fixed an issue where windows that are minimized when the browser is restarted aren’t restored properly.
  • Fixed an issue where Netflix playback fails with error D7356.
  • Fixed an issue where the space bar doesn’t work when typing in the address bar.
  • Fixed an issue where the enter key doesn’t work when typing in the address bar.
  • Fixed an issue where the Windows Hello prompt to log into a website with the user’s OS credentials sometimes shows in an infinite loop.
  • Fixed an issue for users of work and school accounts where websites that try and fail to use the browser profile’s credentials to log in don’t subsequently allow the user to fall back and try the user’s OS credentials.
  • Improved the way Collections export images to Word documents.
  • Fixed an issue where items sometimes fail to be added to Collections.
  • Fixed an issue where webpage contents sometimes render all black if Collections is enabled.
  • Fixed an issue where adding certain images to Collections results in a card with a broken image.
  • Fixed an issue where PWAs installed for one user on a machine sometimes can’t be launched by other users on the machine.
  • Fixed an issue on Mac where feedback screenshots can’t be included when submitting feedback.
  • Fixed an issue where link context menus don’t show all the options if they’re opened via the keyboard instead of the mouse.
  • Fixed an issue where some websites that are pinned to the Task Bar launch new tabs instead of activating existing tabs when tabs with those websites already exist.
  • Fixed an issue where open tabs aren’t properly imported from Chrome.
  • Fixed an issue where the wrong icon appears on web notifications.

 

Known issues: 

 

  • There are some issues where users with multiple audio output devices sometimes don’t get any sound from Edge. In one case, Edge becomes muted in the Windows Volume Mixer and unmuting it fixes it.  In another, restarting the browser fixes it. 
  • At certain zoom levels, there is a noticeable line between the browser UI and the web contents.
  • Last month, some users got a “Work” account automatically added to the browser that wasn’t removable. Although we recently enabled the ability for some users to remove this account, there’s still an issue where users who are signed into Windows with a work or school account may not be able to remove that account from the browser. 
  • Clicking a link on one virtual desktop currently opens a new tab in a window on a different virtual desktop if there’s no window open on the current desktop but there is on another. This is a regression from past behavior, which opened a new window on the current desktop. 
  • Jumplist entries are not consistent between the Start Menu and the Task Bar for some users. We believe this is due to the shortcut on the Start Menu not getting migrated properly after an Edge update and are working on a fix.  Additionally, after getting the update for the new icon, there are still places on the Start Menu, for example when searching, that still show the old icon. Other places like the Task Bar may be able to be fixed by un-pinning and then re-pinning any Edge shortcuts that already exist there. 
  • Sometimes the browser will appear to not respond to any user input (clicking or scrolling in webpages doesn’t do anything, hovering over UI doesn’t make it change), but clicking on certain buttons still works (like the … menu). The cause of this is due to an error in the GPU process, and opening the browser task manager (right-click near the window minimize/maximize/close buttons or hit shift+esc on the keyboard) will open a window that will allow you to end the GPU process, which will fix the issue.  This issue was inherited from upstream Chromium, and a fix for it just went in upstream, so the next Dev update should have it.

 

We won’t be updating next week due to the holidays, but in the meantime we’re very thankful for all your feedback and suggestions! 

 

60 Replies
oh, that's work, but now we should do it manually instead of automatically((
334.4 is still crashing when adding a page to Collections.
Also, now it also closes any pinned tabs on restart. Previous versions didn't do that..... :(
Tab Grouping is still in development

@RobWuijster 

Myself, I have never had anything crash any Channel, BUT...  I did just try to repro the scenarios you have described and I could not.; did not crash & did not close pinned tabs.

Cheers,
Drew

Dev is crashing, Canary is not
" Spell check: Use enhanced spell check " Really need this option.
What will happen when beta and DEV, become the regular edge ?

@steve6980 

Hi Steve,

Currently, we have the 3 beta Channels, Beta, Dev & Canary.  Once Edge C goes GA mid-January, obviously, that replaces Edge HTML.  As for the betas, the Insider Builds, one suspicion is AN Insider (beta) Build will continue, likely as Canary.  This would be similar to having regular Win10 installations whist some are, ALSO, running/testing & giving Feedback on Insider Builds... with stuff that ends up in regular installations.  Some of us think there will continue to be an Insider beta & Edge may continue to evolve & develop through that, similar to the scenario with Win10.

Cheers,
Drew

@steve6980 


@steve6980 wrote:
What will happen when beta and DEV, become the regular edge ?

There will always be Beta/Dev/Canary channels, even after stable version is released, this is just like how Google Chrome works.

https://support.google.com/chrome/a/answer/9027636?hl=en

"Once Edge C goes GA mid-January, obviously, that replaces Edge HTML."
Not really, only happens if you manually and intentionally install stable version on your computer. which at first will be a half-baked browser for months.

 

https://docs.microsoft.com/en-us/DeployEdge/microsoft-edge-sysupdate-windows-updates

The way I understood it, beginning January 15 the new Edge will start to be pushed out to users automatically. If the new Edge is installed through these means, the old Edge will effectively disappear from all entry points in the UI, but it will still be there and so will the EdgeHTML engine, which is still used by UWP apps and more. I think in the long run that one will be replaced by the new engine as well but that is still some ways off - see the documentation for the new Chromium-based WebView 2:

"Developer preview is available for Win32 C++ on Windows 10, Windows 8.1, Windows 8, and Windows 7. In the future, we plan to support WebView2 on .NET, and XAML."

From https://docs.microsoft.com/en-us/microsoft-edge/hosting/webview2

@adrianghc 


@adrianghc wrote:
The way I understood it, beginning January 15 the new Edge will start to be pushed out to users automatically. If the new Edge is installed through these means, the old Edge will effectively disappear from all entry points in the UI, but it will still be there and so will the EdgeHTML engine, which is still used by UWP apps and more. I think in the long run that one will be replaced by the new engine as well but that is still some ways off - see the documentation for the new Chromium-based WebView 2:

"Developer preview is available for Win32 C++ on Windows 10, Windows 8.1, Windows 8, and Windows 7. In the future, we plan to support WebView2 on .NET, and XAML."

From https://docs.microsoft.com/en-us/microsoft-edge/hosting/webview2

 

Yeah the Webview was also the reason why they have been holding off the plan to roll out SETS to Windows 10, because they wanted to use the new Webview 2 based on Chromium for the SETS.

at least that's what I had read about it.

 

https://www.youtube.com/watch?v=3lEjuU-XFHg

 

 

@Drew1903 Hi, Thanks for checking this. I might cleanup & re-install to see if this will help.

You're welcome, Rob. Let me know how that goes..

Cheers,
Drew

PS: My name is Drew; without the @ or the numbers
Version 80.0.334.4 still crashes after startup due to profile sync. When sync is disabled, startup is normal.

At least for me the GPU freeze issue hasn't happened for a good week or two on Beta channel (79.0.309.40). Being stable as it is, I guess I'll keep using this build until Edge goes GA next month.

That's good, things are also fine here on Canary :)
Yes better keep sync disabled because it's currently not working

https://go.microsoft.com/fwlink/?linkid=2080386

I'm also still getting this error, currently on Version 80.0.361.111. 
I know this thread is a bit old, but were you ever able to find a cause/resolution?@subodhpareek18