Dev channel update to 90.0.789.1 is live

Microsoft

Hello Insiders!  Today we’re releasing build 90.0.789.1 to the Dev channel.  Before we get into the changes, we wanted to make sure you knew about the latest status of our password management feature within the Microsoft Authenticator app.  We’ve got all the details here:  https://blogs.windows.com/windowsexperience/2021/02/05/simplify-and-secure-your-life-with-microsofts....  Additionally, for enterprises and IT managers, we know you’ve been eagerly awaiting our kiosk mode work, and we’ve got an update on that here:  https://blogs.windows.com/msedgedev/2021/02/05/what-you-need-to-know-about-kiosk-mode-when-support-f...

Now, for everything in the product: 

 

Added features: 

 

  • Added options for a simplified right-click menu for PDFs.  Note that actual changes to the right-click menu are still being rolled out, so these settings may not be functional yet. 
  • Added management policies for Quick View Office Files Enabled, which controls whether or not Office files can be opened directly in Edge instead of being downloaded, and for Application Guard Favorites Sync Enabled to control whether or not Application Guard windows should have access to the same set of Favorites as non-Application Guard windows.  Note that updates to administrative templates or documentation may not have occurred yet.   

 

Improved reliability: 

 

  • Fixed a hang on shutdown that may prevent Edge from opening correctly. 
  • Fixed an issue on Mac running on ARM where all tabs immediately crash as soon as they’re opened. 
  • Fixed a crash when refreshing a page. 
  • Fixed a crash when exiting fullscreen. 
  • Fixed a crash when interacting with the Shopping popup. 
  • Fixed a crash when dragging and dropping Favorites. 
  • Fixed a crash when using Family Safety. 
  • Fixed a crash when navigating in an IE mode tab. 
  • Fixed a crash when dragging and dropping something into a Collection. 
  • Fixed a crash when removing shortcuts for PWAs or websites installed as apps. 
  • Fixed a crash when uninstalling a PWA or a website installed as an app. 
  • Fixed an issue where uninstalling a PWA or app installed as a website while it’s still running can hang or crash the browser. 
  • Fixed an issue where opening a PDF with Information Protection sometimes crashes the browser. 
  • Fixed an issue where using Web Capture when the F12 Dev Tools are open crashes the tab. 
  • Fixed a hang when starting Read Aloud from the PDF toolbar. 

 

Changed behavior: 

 

  • Fixed an issue with vertical tabs where pinned tabs are always expanded when the vertical tabs pane is expanded. 
  • Fixed an issue where AV1 video sometimes becomes corrupted or drops frames. 
  • Fixed an issue where links from outside applications sometimes open in a brand new browser profile instead of one of the existing ones. 
  • Fixed an issue where Edge Taskbar shortcuts sometimes disappear. 
  • Fixed an issue where shortcuts to PWAs or websites installed as apps sometimes don’t work. 
  • Fixed an issue where desktop shortcuts are sometimes created for PWAs or websites installed as apps when they shouldn’t be. 
  • Fixed an issue where desktop shortcuts to PWAs or websites installed as apps are deleted or no longer work. 
  • Fixed an issue where icons for certain PWAs or websites installed as apps are too small when pinned to the Start menu. 
  • Fixed an issue where the ability to pin a PWA or website installed as an app to the start menu or desktop by right-clicking its entry in edge://apps is missing. 
  • Fixed an issue where uninstalling a PWA or website installed as an app from the Start Menu sometimes doesn’t remove its entry from edge://apps. 
  • Fixed an issue where pending download items sometimes aren’t initially visible in the Downloads popup menu. 
  • Improved the appearance of the Favorites and History menus on small screens. 
  • Fixed an issue when searching for History using the History menu and no results are returned. 
  • Fixed an issue where Settings sometimes shows inaccurate sizes when viewing cookies and site data. 
  • Fixed an issue where links copied from within webpages that are supposed to be formatted with the title of the page aren’t. 
  • Fixed an issue where using Web Capture can sometimes cause scrolling issues. 
  • Fixed an issue where the management policy for New Tab Page Hide Default Top Sites doesn’t work. 
  • Fixed an issue where the management policy for Kiosk Address Bar Editing Enabled does the opposite of what it says it does. 

 

Known issues: 

 

  • Certain extensions such as the Microsoft Editor extension don’t work on Linux.  As soon as they’re installed, they crash and are disabled.  We’re currently investigating. 
  • 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.  This issue should be reduced now that automatic deduplication has been introduced into Insider channels.  However, we’ve also seen duplication happen when running the manual deduplicator on multiple machines before either machine has a chance to fully sync its changes, so while we wait for the automatic deduplication to make it to Stable, make sure to leave plenty of time in between runs of the deduplicator. 
  • 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. 

 

As always, we couldn’t do this without all the valuable feedback you provide! 

 

40 Replies

@HotCakeX I mean, is anything really finished?  At some point we have to decide it's good enough for v1.  Think how long people waited for us to initially release Stable!  I wouldn't be surprised if these widgets will get more powerful in what they can do for themselves in the future, but in the meantime I assume you've also filed feedback about that specific behavior?  

@Quinn Wade just want to clarify, is it the whole browser that's crashing or just the individual tabs?  We've seen an increase in reports of people recently experiencing all their tabs crashing as soon as Edge is opened, but the browser itself is still fine.  

@VladislavKosev the high CPU use is a known issue.  We believe we inherited it from upstream Chromium (https://bugs.chromium.org/p/chromium/issues/detail?id=1176231) and a potential fix was just made that we hope will make it into Canary in time for next week's Dev update.  In the meantime, it appears to be related both to what websites you're on (specifically the active tab) as well as vertical tabs (completely disabling them from the flag seems to help for some people).  

@sid9-3 while we're working on improving password generator's coverage, we've got a form here for any sites you encounter that it doesn't work on:  https://forms.office.com/Pages/ResponsePage.aspx?id=v4j5cvGGr0GRqy180BHbR123cdFSKdZItI7mcVwhTx1UM1FN... 

[High CPU Usage] Interesting. In my case I can verify that adding SSL to the website I am developing and opening them using HTTPS resolves the problem. Not sure how that would relate to rendering labels...

I can run tests if you need help.

@josh_bodner 

Spoiler

@josh_bodner wrote:

@HotCakeX I mean, is anything really finished?  At some point we have to decide it's good enough for v1.  Think how long people waited for us to initially release Stable!  I wouldn't be surprised if these widgets will get more powerful in what they can do for themselves in the future, but in the meantime I assume you've also filed feedback about that specific behavior?  


You are totally right.

yes I have submitted feedback about it

@josh_bodner 

Hi,

just wanted to say this box is back in today's update, version 90.0.796.0 (Official build) canary (64-bit)

 

dsadsa.png

 

@josh_bodner I'm on Surface Pro X, Insider Dev 21301.1010. No change when toggling those flags. Scrolling on touchpad and using the touchscreen is still jerky, like frames are being dropped. Edge Beta 89 doesn't have this issue so I switched down to that.

 

Edit: apologies, I did a hard restart and the problem went away on Dev 90. Probably GPU driver-related issue? I also did a clean install of Dev 90 and the problem didn't show up.

I'm curious about one thing.

When Microsoft want fix the installation path on Windows?

Because, you know when install Edge whatever Dev, Beta, or Stable, the program file location still on "Program Files (x86)," not on "Program Files"

 

I have the images. Both on Stable, Beta, and Dev channel.

 

Can you guys fix this with Chromium team?

@josh_bodner 

Tak popieram tą opinie i zaangażowanie to wszystko zabiera cenny czas .
Pozdrawiam

 

sayalsya2020 @

كلام صحيح هذا مايلزم فعله من المستخدمين حتى يتم تصحيح الأخطاء الشائعة عند التحديث وكل الثقة لك مايكرسوفت الحافه لقد وصلت إلى 

أعلى سرعة آمنه ومتكامله✌:handshake::ok_button: 

@josh_bodner 

sayalsya2020@

كلام صحيح هذا مايلزم فعله من المستخدمين حتى يتم تصحيح الأخطاء الشائعة عند التحديث وكل الثقة لك مايكرسوفت الحافه لقد وصلت إلى 

أعلى سرعة آمنه ومتكامله✌:handshake::ok_button: 
Witam
Ja to widzę inaczej , uważam że nie od razu są problemy ale buforowanie danych powoduje nie właściwe przepływy .
U mnie dopiero później występował błąd i była konieczność zamknięcia programu Edge wielokrotnie na wielu urządzeniach błąd się powtarza i jest podobny do wszystkich.
Witryna nie współpracuje z Edge szczególnie typowo desktopowa mobilne wersje witryn
działają raczej dobrze.
Dziękuję`
Witam
Jest lepiej widzę poprawę =przywracanie kart po nagłym zamknięciu
Edge - działa OK
Ale nadal pamięć poręczna nie współpracuję z systemem Windows ,
Myślę że powodem może być zapora Defender jej niewłaściwa aktualizacja która może powodować zatrzymanie Edge - tak myślę .
Ale ogólnie kierunek jest dobry wiele problemów już nie istnieje !
Jest tu jak w domu bardzo się cieszę .
Pozdrawiam
Originally the whole browser would crash when a new tab was clicked. Now when a new tab is clicked the following message is received. "Hmmm… can't reach this page It looks like the webpage at edge://newtab/ might be having issues, or it may have moved permanently to a new web address." Could this be the result of the update to v90.0.796.0?
ERR_FAILED

Dzień dobry dziwne takie krytyczne zatrzymanie mam tydzień temu do teraz się nie zdarza !
warto przeanalizować Update Windows i wykonać ponowne uruchomienie systemu Windows.
Wiele aktualizacji i konserwacja musi czas mieć na adaptację nowego sterowników !
Pozdrawiam Wszystkich

@Quinn Wade do you have any extensions installed that might be modifying the new tab page?  And can you get the same thing to happen in a new browser profile?  

@josh_bodner Thanks for the reply. No extensions set to modify the browser. Normally the new tab would open blank prior to the upgrade. That's how it currently behaves with the Stable channel. Adding a new profile returns the same result. Version now is 90.0.803.0.

@Quinn Wade would it be possible for you to install Canary and see if the same thing happens there as well?  I'm trying to figure out if it's your device's configuration that's causing this, and if the same thing happens in Canary, that would point to that being the case.  

Looks like the new tab error was related to a GP setting. After updating the setting the error was no longer showing when the new tab was opened in Dev