Dec 17 2019 10:49 AM
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.
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:
Improved reliability:
Changed behavior:
Known issues:
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!
Jan 04 2020 05:40 PM
@davequail
Dave, the current Dev is Version 80.0.361.23
Cheers,
Drew
Jan 04 2020 06:34 PM - edited Jan 04 2020 06:37 PM
@josh_bodner Here's what I've found. You're exactly right, inherited from Chromium Beta 80.0.3xxxx.x builds.
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.
Jan 04 2020 09:35 PM
@davequail wrote:
I am using the current Dev channel which I suspect is really out of date.
Yes you're right
Jan 04 2020 09:37 PM
Beta works just fine. So I'm switching to beta.
Jan 04 2020 09:39 PM
Jan 04 2020 09:56 PM
Jan 04 2020 10:36 PM
@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
Jan 04 2020 11:10 PM
Jan 04 2020 11:28 PM
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
Jan 04 2020 11:51 PM
Jan 05 2020 10:20 AM
Jan 05 2020 11:41 AM
Jan 05 2020 12:32 PM
@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.
Jan 05 2020 12:46 PM
They aren't the same.
top is from Edge classic, bottom is from Edge insider canary
Jan 05 2020 12:48 PM
@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?
Jan 05 2020 12:53 PM
Jan 05 2020 01:07 PM
Jan 05 2020 01:11 PM
@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