Dec 10 2019 10:37 AM
Hello insiders, today we’re releasing build 80.0.355.1 to the Dev channel! Even more exciting, Collections are now enabled by default for all Canary and Dev channel users, as well as Collections sync! This blog post has the details: https://blogs.windows.com/msedgedev/2019/12/09/improvements-collections-sync-microsoft-edge. Please note that some users who have manually modified their sync settings in the past may not have Collections sync enabled and will need to turn it on themselves.
Before we get to all the most noteworthy changes, it’s worth mentioning something that hasn’t changed: favorites sync is still disabled for most people in order to prevent some crashes and favorites duplication. However, if you’re currently syncing with Edge mobile, your favorites sync hasn’t been disabled, so if you’re experiencing Edge crashing shortly after startup, it’s likely that your favorites sync is still enabled.
Added features:
Improved reliability:
Changed behavior:
Known issues:
As always, we appreciate all the feedback and suggestions we’ve collected from you!
Dec 15 2019 11:02 AM
I have the same issue with the virtual keyboard on an ASUS tablet.....URL field is useless in tablet mode
---->It would be nice to have a working keyboard on surface PRO. it's still broken in the URL field since early November
Dec 15 2019 01:26 PM
Dec 15 2019 01:49 PM
I asked for final version of Edge that will be launched in January? Thanks.@HotCakeX
Dec 15 2019 01:51 PM
@Reka731
Yes, absolutely, it will be due to its extreme popularity. AND, There is a flag to enable it, now.
Cheers,
Drew
Dec 15 2019 02:19 PM
Dec 15 2019 02:24 PM
@RedBeta It should work in beta.
The bug was fixed in chromium yesterday so now it's just a matter of MS releasing a build based on chromium 81.0.3997.0 or newer
Dec 15 2019 03:23 PM
@matsmcp
Mat, I have all 3 Channels on 1909 AND 2004. Right now, of the 6, Dev on 2004 does Dark pages, by default. All the others, still, need the flag Enabled. This is another one that is not hitting everywhere simultaneously.
Cheers,
Drew
Dec 16 2019 12:23 AM
Dec 16 2019 01:20 AM
Dec 16 2019 03:38 AM
@davequail wrote:
Hi all, I cannot change the fonts from the standard ones. Version 80.0.355.1 (Official build) dev (64-bit)
Yeah, another issue that wasn't supposed to but moved anyway from Canary to Dev channel. it is fixed now in Canary so Dev channel should wait for its turn to receive the same fixes too, probably in the next Dev update.
Dec 16 2019 11:48 AM
Hi,
Two bugs:
1. Downloading big files (>100MB) crash the browser (try to download some linux image ;))
2. If you have website which using local certificate (installed in trusted folder) browser not allow that page (even with enabled #allow-insecure-localhost flag)
Dec 16 2019 06:05 PM
@Mateusz_Romanowski is downloading the files crashing Edge Dev or Edge Canary? If it's Dev, can you try it in Canary and see if it still happens? I tried downloading some 500MB driver packages with my Edge Dev today and couldn't get it to crash.
Dec 16 2019 10:37 PM
Dec 16 2019 10:46 PM
@josh_bodner I checked only Dev version. I try to check Canary version.
I think maybe it is because I have #enable-parallel-downloading flag enabled? I'll check this also.
Dec 16 2019 10:48 PM
Hi,
On the beginning when I put path to downloaded file (user/downloads it's not my default path - always ask)
Dec 17 2019 03:10 PM
@Mateusz_Romanowski I tried enabling that flag in today's Dev update and couldn't reproduce the crash, so you may want to update and try again yourself. Also, are you running any extensions? Those might be interfering as well.
Dec 18 2019 07:15 AM
@Drew1903 Thank you kindly for trying to reproduce it; my apologies in the delay replying to your sincere testing. I was out of a working system for this week (not related to Chromium Edge, heh).
But, you're exactly right. Controlled "feature rollouts" in testing environments, especially buggy ones that have no discussion or introduction, have always been problematic for testers. It's a win-lose situation where the loss of autonomy by testers is the gain of autonomy by developers. Testers can't begin to write meaningful bug reports because "not reproducible" is a feature of these rollouts--our task as testers, on the other hand, should be engaging the product faithfully & describing its behavior via our access to "live, user" machines with myriads of physical hardware configurations, browser profile settings, and browsing patterns.
When you instead use "feature rollouts", testers are left in the dark. Does "not reproducible" mean it's a third-party issue unique to this system? Does "not reproducible" mean the trigger condition is too rare to produce spontaneously? Or, here, is this just another "feature rollout" that was enabled for just this machine?
Thanks for confirming, @little_terry and @HotCakeX . The same happened on my machine: once they reversed the rollout from this machine, the bug disappeared.
Cheers, @josh_bodner , for the update on what exactly was going on. Definitely the former.
Dec 18 2019 08:01 AM