11-19-2019 10:48 AM - edited 11-26-2019 03:50 PM
11-19-2019 10:48 AM - edited 11-26-2019 03:50 PM
UPDATE 2: We published 334.4 today to more broadly disable favorites sync, which should fix some sync-related crashes that users have been experiencing.
UPDATE: We published 334.3 today to fix an issue where navigation on some websites was taking an extraordinarily long time for some users. We're also hoping to publish another small revision next week to fix a couple of known crashes.
Hello insiders, today we’re releasing build 80.0.334.2 to the Dev channel! The most important thing to know this week is that, after last week’s sync issues, we’ve temporarily disabled favorites sync to prevent any more duplication. As for the other noteworthy changes:
We won’t be updating next week due to the holidays, but in the meantime we’re very thankful for all your feedback and suggestions!
11-19-2019 12:59 PM
@josh_bodner Thanks for finally adding the ability to sort favourites. However the process was not exactly intuitive like it is in the old Edge. In old Edge I could right click on the pop down favourites list. Whereas in the Chromium version I have to go to manage favourites and then search for exactly the right place to right click.
So better than no sorting but no where near as good as the old Edge ... or even IE.
11-20-2019 01:06 AM - edited 11-20-2019 05:04 AM
@josh_bodner Another update, still NO scrolling fixes even a week after scrolling issues were said to be addressed.
Please... just directly translate the ENTIRE scrolling and zooming behaviour from the Classic MS Edge/UWP source code...
To make Classic Edge, how did Microsoft take the Win32-centric Internet Explorer and make the scrolling actually better than every other browser including Safari on iOS (the OS where today's touch scrolling experience originated)?
You need to do the same for Edge Chromium. In part due to Chromium's weird relationship with Win32 and half-hearted attempts to make Chromium's UI platform-agnostic, it has various rendering issues everywhere across the UI (e.g. tooltips were previously rendering with incomplete borders, or the still longstanding issue of the address toolbar having a 2px grey bottom border on HiDPI screens when maximised but not when minimised). I believe these also affect the scrolling behaviour.
Why is Internet Explorer Mode scrolling and zooming 60 FPS within Chromium Edge but Chromium Edge's own scrolling/zooming behaviour terrible in comparison?
I will upload a video comparison of Edge Chromium and Classic Edge/IE Mode rendering and scrolling behaviour later/tomorrow.
THREAD about what needs to be done: https://techcommunity.microsoft.com/t5/Discussions/What-needs-to-be-done-to-improve-scrolling-and-zo...
Please make it a priority to:
If needed I will even work for free to be your scrolling QA Lead...
The quality of scrolling in Chromium Edge, in most if not all areas, is unacceptable. You could make even Internet Explorer's scrolling/zooming perfect. You can do it for Chromium Edge....
11-20-2019 02:40 AM
Just curious, is there a reason that the Overlay Scrollbar is missing from the Flags? i like the hide-able scrollbar but this feature has been missing from the Dev browser for quite some updates now.
11-20-2019 05:54 AM
@josh_bodner "we’ve temporarily disabled sync to prevent any more data duplication."
I checked my settings. Sync is still on. Should I manually disable it if it haven't been disabled automatically? or... Is this change serverside?
Thanks in advance :)
11-20-2019 08:27 AM - edited 11-20-2019 09:00 AM
This update has made Dev almost unusable for me. Sites take forever to load, images are squares until it finally loads the page fully (20sec-1min). Chrome works just fine, etc.
Restarted browser multiple times, restarted PC as well.
Anyone else seeing this?
Update: noticed the last bullet point about the GPU process - this helped for a few minutes but then back to crawling.
11-20-2019 09:10 AM
On Dev and Canary channels, I'm still getting logged out of Disqus whenever I refresh or open a new page. At least the "PlayReady DRM for Windows 10" flag was reimplemented, which needs to be disabled in order to have HD playback on Amazon Prime Video content. Looks like I'll have to stick to Beta build until Edge Chromium goes gold in January.
11-20-2019 09:27 AM
11-20-2019 11:18 AM
11-20-2019 04:11 PM
@Yoneff in case you haven't seen it yet, we've got a discussion going here about what you'd like to see us do with that feature: https://techcommunity.microsoft.com/t5/Discussions/Provide-run-open-save-save-as-options-when-downlo....
11-20-2019 04:15 PM
@Jordan Paris and everybody else seeing this, we finally got this issue root caused today, and it has to do with what kind of TPM your machine has, which is why not everybody is seeing this. The fix for it should be in either tomorrow or Friday's Canary, and we're hoping to also patch Dev with this fix since we aren't doing a full Dev update next week and don't want to leave people hanging.
11-20-2019 06:00 PM - edited 11-20-2019 06:01 PM
Hi, I'm still facing this issue, and have been for weeks
> Fixed an issue where Netflix playback fails with error D7356.
11-21-2019 06:29 AM
11-21-2019 06:35 AM
@josh_bodner -- Does anyone have issues with their profile picture not showing on this build? The previous one was okay, but this build is blank. I signed out and back in to see and even editing it shows the correct picture on MS site.
11-21-2019 04:29 PM
For those who have Canary channel, have the freeze caused by GPU process hanging and Disqus being repeatedly logged out issues fixed?
11-22-2019 10:23 AM
Major issues encountered:
Page load times are awful --> I've moved to Brave only for now.
UI doesn't always respond to clicks as per your GPU note above.
Scrolling still horrible.
On the bright side, I haven't seen the intermittent crashing when testing phishing links that I had prior to this update.
11-22-2019 05:09 PM
Crash on Startup:
Process: Microsoft Edge Canary 
Path: /Applications/Microsoft Edge Canary.app/Contents/MacOS/Microsoft Edge Canary
Version: 80.0.340.0 (80.340.1911200)
Code Type: X86-64 (Native)
Parent Process: ??? 
Responsible: Microsoft Edge Canary 
User ID: 501
Date/Time: 2019-11-22 20:06:50.027 -0500
OS Version: Mac OS X 10.13.6 (17G10017)
Report Version: 12
Anonymous UUID: 11E9AB5D-3FA0-D5B3-80B2-BD63FE863442
Time Awake Since Boot: 93000 seconds
System Integrity Protection: enabled
Crashed Thread: 0 CrBrowserMain Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00002121212121e1
Mac OS X High Sierra
11-23-2019 05:47 AM - edited 11-23-2019 05:50 AM
@millermk At least for me with 125% scaling, they are far too tall for that. Compare these two (the red close button makes it more apparent):
Actually, the old size was closer to that of UWP app title bars for me. But maybe that's because my scaling is different than yours.
11-23-2019 05:58 AM - edited 11-23-2019 05:59 AM
@adrianghc You make a good point (which is why i mentioned closer). I think I associate big with store and small with desktop, even if it's too big, but I'd love to see the title bar match store apps exactly as suggested by adrianghc, and also to see some margin/padding between the close button and the window title (again, to match store apps).
E.g. see YouTube Music running as edge installed app and Microsoft News running as store app:
11-25-2019 07:55 AM
11-25-2019 02:12 PM
11-26-2019 02:49 AM - edited 11-26-2019 02:50 AM
this big title bar started appearing since 2-3 weeks ago, I remember it wasn't so big before that.
I think it's another thing that is caused by a change (unwanted one) in Chromium source.
I just checked Google Chrome canary's UI in focus mode and PWA mode, they look the same, big like that.
at first Edge insider had its own small nice UI but unfortunately Chromium affected it..
11-28-2019 09:43 AM
.346 has fixed the crash on startup. Looks like it was related to the Information/News tab. If I was *real* quick and closed it as soon as I could I could then open a new blank window. .346 is working normally.
11-29-2019 12:43 AM
12-01-2019 07:01 PM
Currently, we have the 3 beta Channels, Beta, Dev & Canary. Once Edge C goes GA mid-January, obviously, that replaces Edge HTML. As for the betas, the Insider Builds, one suspicion is AN Insider (beta) Build will continue, likely as Canary. This would be similar to having regular Win10 installations whist some are, ALSO, running/testing & giving Feedback on Insider Builds... with stuff that ends up in regular installations. Some of us think there will continue to be an Insider beta & Edge may continue to evolve & develop through that, similar to the scenario with Win10.
12-01-2019 08:06 PM
What will happen when beta and DEV, become the regular edge ?
There will always be Beta/Dev/Canary channels, even after stable version is released, this is just like how Google Chrome works.