Dev channel update to 87.0.664.8 is live

Microsoft

Hello Insiders!  Today we’re releasing build 87.0.664.8 to the Dev channel.  This is the last build for major version 87, so except for maybe a small patch or two, this is the build that will soon be going to Beta.  We have one important known issue in this build that’s actually a fix for a previous issue.  A couple of weeks ago, people who were expecting their session to be restored, either because they have Edge set to start up with their previous session or they intentionally checked for updates in Settings, lost their sessions.  Today, the bug that caused that behavior has been fixed, but the fix causes the exact same behavior.  If you’re in that group of people who lost their tabs, there’s a good chance they’re recoverable.  Go to … > History, and look for entries in the “Recently closed” section that mention multiple tabs, since they will restore entire windows.  Other methods, like the ctrl + shift + T, should also work if done right after Edge is opened. 

 

Canary users should also check to see if they’ve been signed out of the browser.  A bug over the last week may have caused that to happen, which will also affect features like sync that rely on being signed into the browser.  Now, for everything noteworthy that’s been added this week: 

Added features: 

 

  • Changed the Favorites menu to now be a pinnable pane that lists all favorites in a single vertical list instead of multiple flyout menus. 
  • Added a price comparison feature to Collections. 
  • Added data recovery to PDFs so that edits or annotations aren’t lost in the event of a crash. 
  • Improved support for AV1 encoded videos.  Note that the Windows extension is still required to be installed from https://www.microsoft.com/en-us/p/av1-video-extension/9mvzqvxjbq9v
  • Added a keyboard shortcut to open and close Collections. 
  • Added a button to the Profile flyout to turn on Sync if it’s not already turned on. 
  • Added a setting to control whether or not the button to reveal passwords on webpages is shown, as well as a management policy for Password Reveal Enabled.  Note that updates to documentation and administrative templates are still needed. 
  • Added a management policy for Kiosk Address Bar Editing Enabled.  Note that updates to documentation and administrative templates are still needed. 
  • Added a management policy for Web Capture Enabled.  Note that updates to documentation and administrative templates are still needed. 
  • Merged the News and Office new tab pages for work and school users.  Note that the Office-only new tab page can still be set for users via management policy. 
  • Rolled out the pre-rendered new tab page more broadly. 
  • Deprecated the management policy for New Tab Page Set Feed Type. 

 

Improved reliability: 

 

  • Fixed an issue where navigating to certain websites crashes the browser. 
  • Fixed an issue where Read Aloud sometimes crashes the browser. 
  • Fixed an issue where Read Aloud on PDFs sometimes crashes the tab.  Note that there is still a known hang with Read Aloud that may cause the tab to eventually crash if it hangs for too long. 
  • Fixed a crash when syncing Collections. 
  • Fixed an issue where dragging items into a Collection sometimes crashes the Collections pane. 
  • Fixed a crash when playing certain videos. 
  • Fixed an issue where certain videos fail to play. 

 

Changed behavior: 

 

  • Fixed an issue where updating Edge causes the current session to be closed instead of restored (if it was set to be restored). 
  • Fixed an issue where users are signed out of Edge after an update. 
  • Fixed an issue where downloaded PDFs always open in Edge instead of opening in the default PDF viewer. 
  • Fixed an issue where the Favorites list sometimes won’t open. 
  • Fixed an issue where some website permissions are unable to be deleted from Settings. 
  • Fixed an issue where items can’t be added to a Collection from within Immersive Reader. 
  • Fixed an issue where disconnecting a monitor while Edge is fullscreen sometimes results in Edge no longer being visible on the remaining monitor(s). 
  • Fixed an issue where Password Monitor sometimes reports different numbers in the alert popup than it does in Settings. 
  • Fixed an issue where websites pinned to the Start menu sometimes don’t show the name of the website. 
  • Fixed an issue where the Taskbar shortcut sometimes looks pixelated or rough. 
  • Fixed an issue where Amazon Assistant doesn’t work when Tracking Prevention is enabled. 
  • Fixed an issue where Open All in Collections sometimes doesn’t work. 
  • Fixed an issue where certain forms on webpages are autofilled when they’re not expected to be. 
  • Fixed an issue where non-password forms on webpages are sometimes detected as passwords. 
  • Fixed an issue where the Web Capture preview sometimes doesn’t match the area selected or shows the area selected to be outside the window. 

 

Known issues: 

 

  • Users of certain ad blocking extensions may experience playback errors on Youtube.  As a workaround, temporarily disabling the extension should allow playback to proceed.  See https://techcommunity.microsoft.com/t5/articles/known-issue-adblock-causing-errors-on-youtube/m-p/14... for more details. 
  • Some users are still running into an issue where all tabs and extensions immediately crash with a STATUS_INVALID_IMAGE_HASH error.  The most common cause of this error is outdated security or antivirus software from vendors like Symantec, and in those cases, updating that software will fix it. 
  • Users of the Kaspersky Internet Suite who have the associated extension installed may sometimes see webpages like Gmail fail to load.  This failure is due to the main Kaspersky software being out of date, and is thus fixed by making sure the latest version is installed. 
  • Some users are seeing favorites get duplicated after we made some previous fixes in that area. The most common way this is triggered is by installing the Stable channel of Edge and then signing into it with an account that has already signed into Edge before.  Fixing this should be easier now that the deduplicator tool is available.  However, we’ve also seen duplication happen when running the deduplicator on multiple machines before either machine has a chance to fully sync its changes, so while we wait for some of the fixes we’ve made to come to Stable, make sure to leave plenty of time in between runs of the deduplicator. 
  • After an initial fix for it recently, some users are still experiencing Edge windows becoming all black.  Opening the Browser Task Manager (keyboard shortcut is shift + esc) and killing the GPU process usually fixes it.  Note that this only appears to affect users with certain hardware and is most easily triggered by resizing an Edge window.  For users with discrete GPUs, updating graphics drivers may help. 
  • Some users are seeing “wobbling” behavior when scrolling using trackpad gestures or touchscreens, where scrolling in one dimension also causes the page to subtly scroll back and forth in the other.  Note that this only affects certain websites and seems to be worse on certain devices.  This is most likely related to our ongoing work to bring scrolling back to parity with Edge Legacy’s behavior, so if this behavior is undesirable, you can temporarily turn it off by disabling the edge://flags/#edge-experimental-scrolling flag. 
  • 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. 

 

Last week, major version 86 was promoted to Stable, so be on the lookout for that! 

 

50 Replies

@josh_bodner 

Thanks for the update, glad to see all those bugs got fixed.

 

It seems that after updating I lost all 150+ tabs (I know it's a lot) and they do not appear anywhere in recently closed tabs. The only tab that was loaded was the "We updated you..." landing page. Did I misunderstand that they should be in there as tab groups with this new bug/fix?

Is there any way to recover my lost tabs? It's going to be difficult to individually find every tab I was keeping.

@josh_bodner Still no history sync... 

@Ryan Buckwalter 


@Ryan Buckwalter wrote:

It seems that after updating I lost all 150+ tabs ... The only tab that was loaded was the "We updated you..." landing page. 


Me too. However, I found Reopen closed window on the window control menu (right-click on the 'title' bar or press Alt-Space). It opened a new window with all my 30+ missing tabs. I don't know how long the option stays there; I was pretty quick in panic mode.

 

@Noel Burgess when I try that it only opens the same window (tweet deck PWA) over and over and over. I tried it maybe 30 times to see if it would go back any further and it doesn't. But thank you for the suggestion.

@Ryan Buckwalter Ah, that's unfortunate.  We've been working on removing PWAs/Apps from the recovery logic for that exact reason:  sometimes it picks up the app windows and not the main one.  Is the list of recently closed windows in edge://history/recentlyClosed any bigger?  

@josh_bodner After the update the recently closed windows list in edge://history/recentlyClosed was completely blank. Now it's filling with sites I've been looking up to try to solve this, but all the previous windows/tab groups are gone.

I do still have the individual history of each site I've been too, so it appears my only option is go through all of that one by one and try to figure out what sites I was trying to keep open.

@josh_bodner I'm noticing in this update pinned tiles in Start are still broken. While the Wide tile is now hidden, the favicon is still stretched to the max size in the tile, where as before it was centered like other Windows apps.

 

lindhartsen_0-1602807906144.png

 

@josh_bodner  The changes to the favorites menu in this release is a big improvement. However, the performance is really bad. It takes nearly 2 seconds for the menu to populate and render after clicking the icon.

@josh_bodner tab groups produce glitchy behavior and get stuck if dragged in the list.

 

WRustenberg_0-1602825995020.png

 

@WRustenberg 

Spoiler

@WRustenberg wrote:

@josh_bodner tab groups produce glitchy behavior and get stuck if dragged in the list.

 

WRustenberg_0-1602825995020.png

 


Yes that's been going on for a while now:

Vertical Tabs visual bug - Microsoft Tech Community

@josh_bodner 
I'm not sure if this is a correct place to ask this but how do I sign-in to techcommunity.microsoft.com using my personal Microsoft account instead of my Teams (school/work) account on Edge Dev? Whenever I try to sign-in, Edge does not give me an option to switch accounts. Instead it directly asks for permissions from my Teams account. I am posting this reply from Google Chrome.

edge.jpg

@josh_bodnerAndroid updated just now, still Chromium 77? It's literally from last summer. Any ETA on when we'll get an up-to-date mobile browser and profile support?

@Anssi Niemi 


@Anssi Niemi wrote:

@josh_bodnerAndroid updated just now, still Chromium 77? It's literally from last summer. Any ETA on when we'll get an up-to-date mobile browser and profile support?


Right on point!

I need to know this too.

Chromium 77 is very old and each Chromium gets a lot of security and bug fixes/patches, not to mention all those new features that's added in each version. (Chromium 77 - 86)

@josh_bodner New favorites menu takes quite some time to load and I don't like it at all.

@foo_bar 

If you want to sign up using your personal MSFT account instead of your work account, you need to first log out of your work account.

 

or you can create a new profile in Edge browser and (optionally) connect it to your personal Microsoft account. you can do it from here: edge://settings/profiles

 

if for some reason you aren't able to do that, you can use InPrivate mode.

 

@josh_bodner Hi Josh, I mean this semi flippantly but also semi seriously - you wrote this "Today, the bug that caused that behavior has been fixed, but the fix causes the exact same behavior. " 

Does this mean the bug is fixed or not? To me, reading it says that the bug is not fixed.

Would have been handy to have proof read this, I think. Would it not be clearer to say "We've attempted a fix in this build but we've since found, it doesn't work - we're working on it further"?

Mike

@HotCakeX Thanks for the reply. Actually, I already only have my personal account in my Edge profile whereas both my personal and Teams accounts are present in Windows 10. So, I'm not sure why Edge chooses only the Teams account for signing-in to techcommunity.microsoft.com. On the other hand, username is asked when singing-in to other Microsoft websites such as manage account, OneDrive and Outlook.