Dev channel update to 80.0.361.5 is live

Microsoft

Hello insiders, today we’re releasing build 80.0.361.5 to the Dev channel!  This is the final build for major version 80, which means it’s also our next Beta channel candidate.  This is also the final Dev channel update for the year; we don’t expect to publish anything more until January.  However, we couldn’t leave you without some holiday treats, so here are all of the feature rollouts that have been recently completed for the Canary and Dev channels. 

 

First, we’ve officially opened up the new Edge Extension Store for submissions!  You can read more about the process for submitting to the store in this blog post:  https://blogs.windows.com/msedgedev/2019/12/16/get-started-extensions-addons-microsoft-edge-chromium

 

Next, for the web developers, we’ve published an example application on our GitHub page that serves as a comprehensive API demonstration of our new WebView2 control.  You can read more about how to use it in this blog post:  https://blogs.windows.com/msedgedev/2019/12/11/webview2-interactive-api-sample

 

For our ARM enthusiasts, we’re bringing our native ARM64 builds to the Dev channel today!  These builds have been in Canary for the last few weeks, and we’ve ironed out most of the major issues during that time.  There’s still one known issue though:  certain DRM video on some websites doesn’t play properly. 

 

If you didn’t see it last week, we made a short post here about some of our work on the Mac touch bar:  https://techcommunity.microsoft.com/t5/Articles/Try-the-revamped-Touch-Bar-experience-on-Microsoft-E...

 

Finally, we’ve got three features to look for in upcoming builds. 

 

  • One of them is what we’re calling the “pinning wizard”. It will occasionally pop up from your Task Bar and suggest top websites from your history to pin directly to the Task Bar as installed websites.  It can also be used at any time from … > More tools. 
  • For users of high contrast themes in Windows, Edge now supports high contrast themes as well! It will follow the theme you’ve chosen in the OS Settings and brings us back to parity with the support offered in Edge Legacy. 
  • And for users of Immersive Reader (formerly known as Reading View), we’ve greatly expanded the number of color themes you can choose from. Many of these are specially designed to reduce eye strain and increase reading comprehension. 

 

Before we get on with the rest of the features and additions that are worth mentioning this week, you should know that favorites sync is still disabled for the majority of users.  This includes brand new machines you install Edge on, so if you’re setting up Edge for the first time and want access to your favorites, you’ll need to manually export your favorites to a file on a different machine and import them on the new one.  We’re also working on a deduplication mechanism once favorites sync is re-enabled, which should prevent new duplicates from coming in as well as remove duplicates for users who have already had their favorites duplicated. 

 

Added features:

 

  • Added support for Dolby Vision playback.
  • Enabled users of Windows Mixed Reality to view 360° videos on VR headsets.

 

Improved reliability:

 

  • Fixed a crash when opening certain PDFs.
  • Fixed an issue where clicking on the Feedback button crashes the browser.
  • Fixed a browser crash for users of Collections.
  • Fixed a crash when closing the browser.
  • Fixed an issue where typing passwords into password fields sometimes causes a tab crash.
  • Fixed a crash when playing the Surf game.
  • Fixed an issue where certain websites don’t load properly.
  • Fixed an issue where Netflix playback fails for certain videos with error D7381.

 

Changed behavior: 

 

  • By request, favorites folders are now yellow.
  • Updated Adobe Flash to version 32.0.0.303.
  • Fixed an issue where PDFs that fail to save for some reason end up failing silently instead of showing an error to the user.
  • Fixed an issue where the font dropdown in Settings doesn’t work.
  • Fixed an issue where the search engine can’t be edited because the Save button doesn’t work.
  • Fixed an issue where the current display language can be removed from Edge even though it shouldn’t be.
  • Fixed an issue where Edge installations on Azure Active Directory domain-joined machines get signed into the wrong account on first run.
  • Fixed an issue where some webpages aren’t able to be translated, and instead show an error saying that the source language and target language are the same.  
  • Fixed an issue where Learn More links clicked during the First Run Experience open in tabs hidden behind the FRE instead of in a dialog above it.
  • Fixed an issue where navigation to certain websites in IE mode sometimes fails.
  • Fixed an issue where adding an item to a Collection sometimes doesn’t load the image properly and instead shows the loading spinner forever.
  • Fixed an issue where pasting items from one Collection into another doesn’t paste them in the correct order.
  • Fixed an issue where dragging and dropping an image into a Collection sometimes results in the wrong link being saved.
  • Fixed an issue where feedback screenshots sometimes don’t work properly on Mac.
  • Fixed an issue where the keyboard shortcut for saving a PDF doesn’t work on Mac.
  • Fixed an issue where desktop notifications are broken on Windows Insider builds.
  • Fixed an issue where Edge sometimes fails to automatically update on Windows Insider builds.
  • Fixed an issue where uninstalling and reinstalling Edge sometimes results in it no longer being able to launch on Windows Insider builds.

 

Known issues: 

 

  • Navigation in new tabs sometimes fails, either showing an error that the connection is closed, or crashing the tab. In some cases, subsequent navigations in the tab are okay. 
  • After an initial fix for it recently, some users are still experiencing Edge windows becoming all black. UI popups like menus are not affected, and opening the Browser Task Manager (keyboard shortcut is shift+esc) and killing the GPU process fixes it. 
  • Highlighting text in the address bar then clicking on webpages sometimes causes black-on-dark text when the browser is in Dark Theme.
  • The Settings page appears too big/zoomed in on certain machines.
  • Some users are still not seeing Collections being enabled by default on Canary and Dev. For users who want to try Collections, enabling the flag at edge://flags/#edge-collections should still work to turn on the feature. 
  • 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.
  • 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. 

 

Thank you for a great 2019 and for all of your help building both this community and the new Edge.  We couldn’t have done it without you! 

 

177 Replies

@davequail 

Dave, the current Dev is Version 80.0.361.23

Cheers,
Drew

@josh_bodner Here's what I've found. You're exactly right, inherited from Chromium Beta 80.0.3xxxx.x builds.

 

  • Chrome Stable (Chromium 79.0.3945.88): no bug
  • Edge Dev (prior Chromium 80.0.355.1): no bug (IIRC)
  • Chrome Beta (Chromium 80.0.3987.16): scroll repaint bug
  • Edge Dev (Chromium 80.0.361.5/9): scroll repaint bug
  • Chrome Dev (Chromium 81.x.x.x): no bug
  • Legacy Edge Stable (44.18362.449.0): no bug
  • Firefox Stable (71.0): no bug
  • Internet Explorer Stable (11.535.18362.0): no bug

The bug has been fixed in Chrome Dev (81). Once Edge Chromium stable launches, I imagine it'll be Stable 79 / Beta 80 / Dev 81 / Canary 82. For the beta testers, maybe the Beta 80 build will be updated so it doesn't exhibit the same bug from our Dev 80 build.

@davequail 


@davequail wrote:
I am using the current Dev channel which I suspect is really out of date.

Yes you're right

Beta works just fine. So I'm switching to beta. 

Yeah Between December 17 and January 5, there has been no major update yet.

@Drew1903 @HotCakeX Thanks Drew, mine only updated to 80.0.361.23 about 2 hours back.

Good ^^

@davequail 

You're welcome, Dave.  (For me) It came to Dev on 1909 quite a long while ago.  I switched to 2004  a couple of hours ago, at least... its Dev, I just updated, now, to .23  

It may have been available there for some time; I can't be sure as was doing non-computer things, as well, looked back (at the PC) & noticed it.

Cheers,
Drew


@Drew1903 @HotCakeX @Havret So far so good with Sync. All three of my PC's are correct as far as Favorites go...

Hopefully it will stay that way

@davequail 

 

Good news, Dave.  As I'd said earlier, in my case, I haven't had Favorites repopulating or showing duplicates multiples for a long time not, in any Channel.  At the time it was suggested it was in the same sphere as the Fav syncing causing crashes. And, it, actually, may have stopped around about the same time as the Team shut off Favs sync... whilst they tried to stop it causing crashes (for some people); I never had that behavior.

Cheers,
Drew

When favorite sync, which is still in controlled feature rollout, is not available in your browser, you obviously don't see favorites duplicated or anything happen to them.
Is there any ETA on the GPU bug fix? It's driving me mad having to open the task manager every 5 minutes to kill the process. That's no exaggeration, either.

80.0.361.23
Let's hope tomorrow Monday, the Edge developer team get back to work and release the next major update for Dev channel..

@HotCakeX "Yellow is a copy of Chrome." UWP Edge and File Explorer both use yellow folders. I could just as easily say that the clear folders were a copy of Opera.

They aren't the same.

top is from Edge classic, bottom is from Edge insider canary

 

gfgf.png

 

@josh_bodner Who knew the folder icons would be such a hot topic? When they were clear glyphs, you heard from all the people who wanted them yellow. Now that they're yellow, you hear from all the people who want them clear. 

Yes, you could satisfy the tiny percentage of users who care by making it an option (perhaps under the Appearance settings). And if you did, well that would be cool—I'm not saying it wouldn't. But is it that important? Chrome has yellow folders. It's not an option and they're not asking anyone's opinion about it. And yet 60% of all web users are happy using Chrome; they take whatever Google gives them. Opera has clear folders and has about 1.5% market share (astonishingly, less than half that even of UWP Edge, which has yellow folders). Is there a causal relationship here? Obviously not. Very few users care (many probably don't even notice.) So why should Microsoft sweat over this?

Nobody knew it would become a hot topic because they weren't planned nor supposed to be changed because of few people.
there is no clear poll, no numbers, showing how many people actually want and how many people are against a change.

Don't confuse the numbers. Chrome might have 60% users but that doesn't mean all of them are happy about everything in the browser.
huge part of that number is because of the Android OS and how Google chrome can't be uninstalled from the OS, only disabled.

Hi Jordan,

Yes, crazy the amount of time and discussion this has had. Not only it is the familiar to Chrome, it is, also, the familiar, the norm for a long time for Windows, IE and Edge.

Yes, indeed, I, too, always find it comical when people seem want something, get it and then hear, oh no don't want that LOL. Come on folks make up your mind (just joking about). Anyway, the traditional colour and realism is just as fine as it's always been.

We could always move on to other things...

Cheers,
Drew

Sent from Windows Mobile

@Drew1903 wrote:
Yes, crazy the amount of time and discussion this has had. Not only it is the familiar to Chrome, it is, also, the familiar, the norm for a long time for Windows, IE and Edge.

Yes, indeed, I, too, always find it comical when people seem want something, get it and then hear, oh no don't want that LOL. Come on folks make up your mind (just joking about). Anyway, the traditional colour and realism is just as fine as it's always been.

We could always move on to other things...

Cheers,
Drew

Sent from Windows Mobile

 

I don't see how the difficulty and problems that people are experiencing seem funny to you and make you laugh!

 

Be sure that those that asked for it Are Not the ones that are now asking to revert it back the way it was before.

 

Sent from Android Mobile