Dev channel update to 80.0.355.1 is live

[josh_bodner]

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:

• Added an option to Reading View to increase text spacing.
• Added a prompt to verify work or school accounts that are automatically added to Edge but aren’t enabled for sync so that users are aware sync isn’t enabled.

Improved reliability: 

• Fixed an issue where closing a window sometimes crashes the browser.
• Fixed a crash on startup on ARM64 devices.
• Fixed a crash that occurs when favorites sync is enabled.
• Fixed an issue where closing a tab too quickly after adding an item to a Collection sometimes crashes the browser.
• Fixed an issue where a crash in the Collections pane causes all future additions to Collections to fail until the browser is restarted.
• Fixed a tab crash.
• Fixed an issue where Edge on Mac fails to install updates automatically.
• Fixed an issue where saving a PDF that has been written on with ink sometimes results in a corrupted file.
• Fixed an issue Application Guard windows fail to open after a browser update.

Changed behavior:

• Updated the toolbar Feedback icon to be consistent with other Windows feedback icons.
• Changed the color of the title bar of installed websites and PWAs to be the dominant color of the site’s favicon.
• Fixed an issue where manually importing data from Chrome isn’t possible if there are too many Chrome browser profiles to fit in the dialog.
• Fixed an issue where the UI and web content is sometimes seen doubled and shrunken on high DPI displays.  
• Fixed an issue where importing favorites from a file sometimes causes any favorites on the Favorites Bar not to be imported directly onto the Favorites Bar.
• Fixed an issue where the Find bar sometimes disappears when the browser loses focus.
• Fixed an issue where the 1px border on top of the window is missing.
• Fixed an issue where the prompt to autofill a credit card has two checkboxes to save the card locally.
• Fixed an issue where navigating to the Sync Settings page always triggers a dialog to enable sync.
• Fixed an issue with changing the order of items in a Collection.
• Fixed an issue where switching tabs quickly after adding an item to a Collection causes the item not to be added properly.

Known issues: 

• The Settings page appears too big/zoomed in on certain machines.
• 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. 

As always, we appreciate all the feedback and suggestions we’ve collected from you! 

[#2]

@ikjadoon , @Drew1903 , @RicoViking9000

Thanks everyone for letting us know about the issues with NTP. Are you still experiencing these with the most recent Canary updates? If so, I will chat with our engineers about next steps.

Fawkes (they/them)
Project & Community Manager - Microsoft Edge

[#3]

@Deleted 

Myself, I only ran into just one very specific scenario.  It, still, exists.  Web pages are Dark without a flag enabled for both Dev & Canary on 2004, exclusively.  This is not the case on 1909.  Other than that no issues, at all.  And, should be noted, tested same on someone's 2004 in Florida and their's did not stay Dark with the flag set to Default.  Certainly, inconsistency is nothing new or strange to us.

And, now, on my own 2004, as well, both Dev & Canary are only Dark with the flag Enabled.  That part is behaving properly (mystically & suddenly). However, both are, still, requiring the Collections flag.

But, no issues with NTP not, now or previously.  If we have to have a NTP, wish is was actually, Bing.com.  By the same token, being a Bing Insider, I have recommended the same Custom choices for Bing.com as there are for the NTP.

Cheers,
Drew

[#4]

If the NTP is going to get the theme of the default search engine then we should be able to change that to any search engine we want. such as DuckDuckgo.

[#5]

@josh_bodner 

It's a late reply but actually after canary version 35x, the Edge insider share the same compatible issue just like chrome. Such issue cause pages even settings cannot be opened correctly. I ran with win 8 compatibility mode as a temporal fix but then the login in profile settings will be disabled. Since there is no telling how long will it take for this to be resolved, I believe you should add it in known issues/FAQ. I took the reference below and changed chrome to edge to fix it, and login in settings seemed to work fine.

https://support.symantec.com/us/en/article.tech256047.html

[#6]

Hi,
do you know whether it's only Symantec that is having problem with browsers or are there other companies that have the same compatibility issues? for example the Kaspersky, Bit defender etc?
because if it is only Symantec, i think they should also do something to fix this issue and not just wait for browsers to do it.

[#7]

@Deleted Thank you for listening.

I think after the feature rollout was halted, I've not experienced any similar or any issues otherwise with the NTP. 

[#8]

@HotCakeX I'm not sure if that's the only reason. When I looked up in this forum and Google, it doesn't seems to be specifically the antivirus' problem, but as far as I concerned there are already 3 discussions regarding the same issue.

[#9]

I know and most of them, if not all, had the same Symantec solution. so i was wondering if for example better AV software like Kaspersky had the same problem too or not