Dev channel update to 83.0.474.0 is live

[josh_bodner]

Hello insiders, today we’re releasing build 83.0.474.0 to the Dev channel.  Believe it or not, this is actually going to be one of the last builds for major version 83, in accordance with our updated release schedule here:  https://blogs.windows.com/msedgedev/2020/03/20/update-stable-channel-releases/.  We’ve also got a nice long article here detailing our work on scrolling:  https://blogs.windows.com/msedgedev/2020/04/02/scrolling-personality-improvements/.  As for everything else that’s worth mentioning:

Added features: 

• Added the ability to show which folder a favorite is in when you search for a favorite on the Favorites management page and then right click a result. 
• Added the ability to create a list of sites that are exempt from the deletion of cookies when the browser is configured to delete browsing data upon closing. 
• Added an option to use quieter website notifications that don’t show unprompted popups. 
• Added a search box to the Mac Touchbar when there is only one tab open. 

Improved reliability: 

• Fixed an issue where typing in the address bar sometimes crashes the browser. 
• Fixed a crash when closing the browser. 
• Fixed an issue where the browser sometimes crashes when showing the Guided Switch popup. 
• Fixed an issue where exporting a Collection to Word sometimes crashes the browser. 
• Fixed an issue where exporting a Collection to Excel sometimes crashes the browser. 
• Fixed an issue where the browser sometimes crashes on launch when Application Guard is enabled. 
• Fixed an issue where navigating in an Application Guard window sometimes crashes the browser. 
• Fixed an issue where the Downloads management page sometimes crashes. 
• Fixed an issue where attempting to use the F12 Dev Tools in a language that’s different than the browser’s language sometimes causes the Tools to fail to launch. 
• Fixed an issue where websites sometimes hang when trying to load if Information Protection is enabled. 

Changed behavior: 

• Fixed an issue where feedback screenshots are all black if the media autoplay blocking setting is set to Block. 
• Fixed an issue where menus like the … menu are sometimes displayed incorrectly near screen edges. 
• Fixed an issue where typing in the address bar while the left mouse button is pressed results in characters not being properly typed. 
• Fixed an issue where a tab that’s restored after restarting the browser will navigate to the same page when the back button is clicked if the page that was restored was blocked by SmartScreen before the browser restart. 
• Fixed some issues around interacting with windows for websites that are pinned to the Taskbar. 
• Fixed an issue where websites that should be viewed in IE mode are sometimes opened in regular tabs instead. 
• Fixed an issue where Guest mode is still available when the Force Sign In management policy is enabled. 
• Fixed an issue where an image sometimes won’t be added correctly to an item in a Collection and instead it will just show a loading spinner. 
• Improved messaging when using the Command+Q keyboard shortcut on Mac.  See https://techcommunity.microsoft.com/t5/articles/macos-blog-improved-messaging-on-the-command-q-alert... for more details. 

Known issues: 

• 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.  We hope that this will be improved once version 81 is released to Stable. 
• Some users are seeing high CPU use in tab or extension processes.  Usually, ending the process, for example via Task Manager, reduces the CPU use back down to normal.  We are currently investigating, and a set of steps to reliably reproduce this behavior would help us if anybody has some. 
• 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. 
• 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. 
• At certain zoom levels, there is a noticeable line between the browser UI and the web contents.

We appreciate your patience as we work through these trying times! 

[#2]

Task Manager in Microsoft Edge is great for internal investigation but sometimes it is an issue with the main Microsoft Edge process and external dependencies, for example recently, I was investigating performance issue and it was conflict with old driver with Microsoft Edge browser and in such a case we couldn't use task manager inside Microsoft Edge.

However, if there is need to investigate process of Microsoft Edge and internal extensions and website, internal task manager is good tool.

[#3]

I know all that, but the users said it's caused by extensions and browser task manager is better for it.

[#4]

@Reza_Ameri-Archived 

Spoiler

---

@Reza_Ameri-Archived wrote:

Feedback is the best way to help people in Microsoft Edge team investigate the problem.

---

Looks like the problem is solved, that's good news

https://techcommunity.microsoft.com/t5/discussions/dev-channel-update-to-83-0-474-0-is-live/m-p/1297...

[#5]

@TrafGib 

Spoiler

---

@TrafGib wrote:

@HotCakeX 

Likewise with gaming mouse & scroll-wheel. I see zero difference, so maybe it is a touch thing, which I don't have on my desktop. My grief with Edge is that the scroll-wheel always advances the screen several lines at a time, seemingly based on the Windows settings for number of lines to scroll. If there is going to be an OS disconnect to make Edge agnostic, then I am not sure where the number of lines to scroll will, or does, come from. With all the discussion around "smooth scrolling", I have been looking for Edge to perform like Firefox does in that the screen scrolls by micro portions of a single line rather that several full lines at a time. The jumpy, jerky, several lines advancing in a scroll is the antithesis of "smooth scrolling". 

---

for me Firefox scrolling seems a bit off, when I compare Edge legacy and Firefox together, Firefox has few milliseconds delay whereas Edge legacy has instant reactions. my mouse has 1000hz Polling Rate.

the Edge however is pretty much the same as Firefox for me. I haven't tested all of the scrolling-related flags though, judging by the default behavior of Edge canary so far

[#6]

@HotCakeX 

At least with Firefox you can edit the smooth scrolling feature, with any Chromium browser you have the option to have it on or off - that's it.

If those are the only options I'd like the "smooth" scrolling to be smoothed out more for mouse users, right now it's too bumpy/jerky.

The best smooth scrolling you can get with Chromium browsers right now is the SmoothScoll addon.

[#7]

@josh_bodner great to see that the cookie clean exception has been added :) (I was one of them asking for it ;) ) :smiling_face_with_smiling_eyes::thumbs_up: ....my current list: 

[*.]linkedin.com

[*.]login.live.com

[*.]microsoft.com

[*.]outlook.com

[*.]sharepoint.com

[*.]yammer.com

[#8]

@Paul Fijnvandraat 

Spoiler

---

@Paul Fijnvandraat wrote:

@josh_bodner great to see that the cookie clean exception has been added :) (I was one of them asking for it ;) ) :smiling_face_with_smiling_eyes::thumbs_up: ....my current list: 

[*.]linkedin.com

[*.]login.live.com

[*.]microsoft.com

[*.]outlook.com

[*.]sharepoint.com

[*.]yammer.com

---

Hello,

do we need to manually wildcard them?

because I set them only like:

• Microsoft.com
• live.com
• Microsoftonline.com
• Office.com

and Edge automatically whitelists all subdomains, at least it seems that way.

[#9]

@sgilder 

Spoiler

---

@sgilder wrote:

@HotCakeX 

At least with Firefox you can edit the smooth scrolling feature, with any Chromium browser you have the option to have it on or off - that's it.

If those are the only options I'd like the "smooth" scrolling to be smoothed out more for mouse users, right now it's too bumpy/jerky.

The best smooth scrolling you can get with Chromium browsers right now is the SmoothScoll addon.

---

I need to test these new flags and see which one makes scrolling different for me using mouse

[#10]

@HotCakeX 

Which flags are you referring to? I feel like much of that post is referring to touch based scrolling. The % based scrolling stuff made no difference for me on other Chromium based browsers and I don't see them in Edge Dev right now.

[#11]

@josh_bodner 

I am using the latest DEV and the sites I setup are not being retained after browser closure. I have created my list twice now. Once the browser is closed the list is not retained.

[#12]

@josh_bodner 

Bug : Help and Feedback >> Report site as safe crashes the browser instantly.

[#13]

@TrafGib just to be clear, which list of sites are you talking about that aren't getting saved when you close the browser?  

[#14]

@drvortex this crash should be fixed in this week's Dev.  

[#15]

@josh_bodner 

Privacy & Services > Clear Browsing Data > Cookies & Other Site Data > Do Not Clear

The domain names that I manually add here disappear on browser restart. For example, if I add [*']live.com to the list, it remains as long as the browser is running. Exit & start the browser again and the list is empty.

[#16]

@josh_bodner 

Likewise, the same manually created list of sites appears under Site Permissions > Cookies & Site Data > Allow and will disappear on browser restart.

[#17]

@TrafGib if you try just a single website instead of using wildcards, does it work?  I see a ' character in your example above, so it might be the URL isn't valid, and that's why it's not saving.  

[#18]

@josh_bodner 

Sorry, typo on my end. I can try any of the following and they all fail to save.

[*.]live.com

live.com

outlook.live.com

www.outlook.live.com

https://outlook.live.com/

I tried each variation, one per per browser close and reopen, and each fails to be saved.

Extensions:

Bitwarden, uBlock Origin, Cookie AutoDelete, Decentraleyes, and HTTPS Everywhere