CyberTech

Level 23
Verified
Microsoft is hard at work on getting the new Chromium-based Edge browser ready for prime time, and while the company is currently updating Canary and Dev builds regularly, no specifics have been provided as to when we could expect the stable browser to ship.

But according to a recent discovery revealed by Microsoft watcher Rafael Rivera on Twitter, the latest Windows 10 preview build for Fast ring insiders comes with code suggesting the Chromium engine could become the new Windows default browser in the 20H1 update.

Windows 10 20H1 preview builds are currently being tested with help from Windows insiders in the Fast ring. The most recent preview build is 18936 and shipped earlier this week.

The discovery indicates that the original Microsoft Edge, the one that’s currently available in the stable versions of Windows 10, would be hidden in the 20H1 update, while the Chromium-based sibling would become the new default.

Windows 10 20H1 due in the spring
If this is true, the Chromium browser should be finalized by the time the 20H1 update is completed as well.

As per Microsoft’s typical schedule, Windows 10 20H1 is projected to be ready in March 2020, while the public rollout should kick off in April or May the same year.

The Chromium Microsoft Edge is also available on macOS thanks to the migration to a cross-platform browser engine. A Linux version of the browser could also be developed, albeit for the time being, Microsoft is yet to publicly announce any plans in this regard.

Meanwhile, users can download Dev and Canary builds of Microsoft Edge on Windows 7, Windows 8.1, Windows 10, and macOS. If everything goes according to the plan, beta builds could ship later this year, ahead of the stable version that’s supposed to be included in the 20H1 update for Windows 10.
Source
 

rockstarrocks

Level 20
Verified
They don't, as WebView is independent from Microsoft Edge, not to mention is also being updated with the new engine.

Microsoft even wants to get rid of IE, with the IE integration into the new Edge.
Isn't the Webview simply Edge HTML, which is basically the core of Edge.
 
  • Like
Reactions: oldschool

rockstarrocks

Level 20
Verified
It uses Edge HTML, but doesn't mean it needs Microsoft Edge, has it's own API.

And has said, Webview is going to be updated with the new engine as well, is up to each individual developer to use it.
"Existing UWP apps (including PWAs in the Store) will continue to use EdgeHTML/Chakra without interruption."
Aka the rendering engine and JavaScript engine which is basically the whole browser. In the Windows 10 20H1 build they will just add (and enable it) a registry value to hide the old Edge from the user, in the start menu.
And we all know if the devs are given the option to use something new or just stick with something they already are using, they will continue to use the old thing until it's EOL.

https://www.reddit.com/r/Windows10/comments/a3pt19
 

Local Host

Level 19
Verified
"Existing UWP apps (including PWAs in the Store) will continue to use EdgeHTML/Chakra without interruption."
Aka the rendering engine and JavaScript engine which is basically the whole browser. In the Windows 10 20H1 build they will just add (and enable it) a registry value to hide the old Edge from the user, in the start menu.
And we all know if the devs are given the option to use something new or just stick with something they already are using, they will continue to use the old thing until it's EOL.

https://www.reddit.com/r/Windows10/comments/a3pt19
You not saying anything I don't know already nor it disaproves anything I've said, EdgeHTML is the engine it runs on, it's far from the whole thing.

You saying as if WebView is going to open the whole browser, when in fact it's going to run on it's own frame on EdgeHTML, if you had coded for UWP you would know this already.

Unless you trying to claim Microsoft won't be adding the new engine to WebView,
Existing UWP apps (including PWAs in the Store) will continue to use EdgeHTML/Chakra without interruption. We don't plan to shim under those with a different engine. We do expect to offer a new WebView that apps can choose to use based on the new rendering engine.
As I said before,
It uses Edge HTML, but doesn't mean it needs Microsoft Edge, has it's own API.

And has said, Webview is going to be updated with the new engine as well, is up to each individual developer to use it.
 
Last edited:
  • Like
Reactions: oldschool

rockstarrocks

Level 20
Verified
I don't know how simple I can make it. I said Edge is not going anywhere in the near future, you disagreed. Edge will be hided, using a registry key addded, in the Windows 10 20H1 not removed for the time being. User can just disable the registry to have Edge back in start menu. Hiding is not equal to removing something, especially when it can be re-enabled easily. I will not reply any further. Good day to you.
 
  • Like
Reactions: oldschool