Dev channel update to 87.0.637.0 is live

[josh_bodner]

Hello Insiders!  Today we’re releasing build 87.0.637.0 to the Dev channel.  It’s a small week this week due to the holiday last week, but we do have some fun things to share about the launch of the Surface Duo.  Here, we have an overview of how Edge works better with multitasking:  https://blogs.windows.com/windowsexperience/2020/09/10/the-new-microsoft-edge-on-surface-duo-showcas....  And for developers, we’ve got an overview of how those dual screen APIs work and how they can get them working in their own websites:  https://blogs.windows.com/msedgedev/2020/09/14/introducing-dual-screen-foldable-web-apis/.  Developers also get a bonus:  an overview of our new source order viewer in the F12 tools:  https://blogs.windows.com/msedgedev/2020/09/15/source-order-viewer-edge-devtools/.  As for everything in the browser: 

Added features: 

• Added the ability to swipe downward on touchscreens to activate Shy UI. 

Improved reliability: 

• Fixed a crash due to sync. 
• Fixed an issue where changing the browser’s theme and then using Shy UI crashes the browser. 

Changed behavior: 

• Fixed an issue where the Cookies and Site Permissions Settings page is blank. 
• Fixed an issue where the Collections pane is sometimes blank. 
• Fixed an issue where right-clicking on items in the right-click menu doesn’t select them. 
• Fixed an issue where some websites like Kaltura show an error that the browser is blocking 3rd party cookies. 
• Fixed an issue where attempting to enter Immersive Reader results in an error on certain pages. 
• Fixed an issue where using the Save As option when downloading a file causes the file location prompt to show the same folder every time it first opens instead of the most recently used folder.
• Fixed an issue where translating content on a page with multiple languages sometimes gives an error that the language it’s being translated to is the same as the current language, even though there is some text on the page that can be successfully translated. 
• Fixed an issue where uninstalling a website installed as an app from outside of Edge (for example, from the Control Panel) sometimes doesn’t cause the app to be removed from Edge’s list of Apps. 
• Fixed an issue where Caret Browsing stays enabled after the browser is closed. 

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. 

As always, you’re the ones who make all this possible!  To better know how we can serve you, we’d love for you to take our quarterly survey here:  https://techcommunity.microsoft.com/t5/surveys/quarterly-survey-september-2020/m-p/1658897. 

[#2]

Hey @josh_bodner thanks for the attention.

When I use Firefox it never autoloads, it's responsive while switching between tabs but use lots of resources. On the contrary Chromium (my primary browser) is efficient but not agile while opening/switching between tabs/new tabs after some time. 

From your point I suppose autoloading is due to low memory availability. 

But make it instantaneous while opening new tab.

[#3]

@gaggleweed Don't worry, you should be getting a fix soon:  https://twitter.com/MSEdgeDev/status/1307012928592211969

[#4]

@jateruy You're not the only person seeing this.  In fact, I can actually repro it here on this site!  We've got somebody looking into it.  

[#5]

@sid9-3 Ah okay, you're comparing to a non-Chromium based browser, that's good to know.  Firefox is actually really interesting since they have a completely different process model.  In them, every tab is in the same process, so they can't shut down or pause the processes the same way we can when you switch tabs.  That very likely contributes to the snappy switching you're used to:  https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Multiprocess_Firefox

[#6]

@josh_bodner That's interesting. 

Bdw the ''sleeping tab'' feature you mentioned is interesting. What I understood from my limited interaction with it is, it will enable the user to personalise resource usage and when a tab/site reloads. So a balance between efficiency and performance, right?

-Smooth scrolling (of course it's in the pipeline) should be the priority as it makes the overall experience smooth.

-The icons in the Edge UI needs fluent touch. In your presentations they look very smooth, a bit thick (I'm failing here to mention the particular design language for the word ''thick''), soft and textured. Currently I find the icons thin (again I hope you understand the difference between thick and thin in design language as I am no expert) and rough.

[#7]

@sid9-3 yes, the goal with sleeping tabs is for us to use as little memory as possible while still having no noticeable speed difference when doing things like switching between tabs.  It's a tough tradeoff, since devices with different amounts of memory and users who use different amounts of tabs in different ways mean that there's not a "set" point that's perfect for every single user.  That will also be why, once we start rolling out sleeping tabs, it will be very important for us to learn if there are any websites that don't respond well to being put to sleep (or more specifically, that don't wake up properly or are broken when they wake up), since we can also fine-tune our heuristics to learn what tabs not to put to sleep at all.