New
#1541
My sync was turned off after updating.
Web developers: We've added a new experimental flag to use WebGPU in Microsoft Edge (and other Chromium browsers). This is currently only available in Canary. Enable the "Unsafe WebGPU" in edge://flags to try it out, and let us know what you think!Tweet
— Twitter API (@user) View on Twitter
Note: As GPU sanboxing isn't implemented yet for the WebGPU API, it is possible to read GPU data for other processes. Use this flag with caution.Tweet
— Twitter API (@user) View on Twitter
I assume that is so it can update. A few times my PC has been idling and I returned to find Edge updated. Chrome has this as well.
Told ya, the flag to enable the QR code generator is now available in Edge Canary (81.0.368.0):
By the way, Chrome Canary is ahead of Edge Canary for about 5 builds and in Chrome Canary this feature still doesn't work well, so don't expect it to work well in the new Edge. After this feature starts working correctly in Chrome Canary, you will have to wait approximately 5 days for the same thing to happen in Edge Canary.
Last edited by LEOPEVA64; 18 Dec 2019 at 20:07.
Doesn't work in Edge either!
This is getting painfully monotonous!
It seems that the "Show greeting" option and the revamped NTP of InPrivate mode are no longer part of the "controlled roll-outs", both features are available in Canary and Dev on all my devices.
Version 81.0.369.0 (Official build) canary (64-bit) edit: corrected build number
Favorites and Collections sync are both turned on in this build.
Last edited by galileo; 19 Dec 2019 at 18:19.
Most insiders will not have noticed, but in the Canary and Dev versions there is a small bug that happens when setting a system scale greater than 100% (150%, 175%, etc.), by doing this, the line that separate the toolbar from the content of the pages (called "toolbar-web contents separator") has a black color:
Of course, the bug is more noticeable in the Light theme:
Well, there is good news for those who are bothered by this small bug, Chromium engineers have already fixed this bug in Chrome Canary and Chrome stable, so the fix should reach Edge Canary in a few days.
PS, In a few cases, it seems that the bug also occurs when the system scale is set to 100%.