Forum Discussion
Dev channel update to 80.0.334.2 is live
steve6980
Hi Steve,
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.
Cheers,
Drew
"Once Edge C goes GA mid-January, obviously, that replaces Edge HTML."
Not really, only happens if you manually and intentionally install stable version on your computer. which at first will be a half-baked browser for months.
https://docs.microsoft.com/en-us/DeployEdge/microsoft-edge-sysupdate-windows-updates
- The way I understood it, beginning January 15 the new Edge will start to be pushed out to users automatically. If the new Edge is installed through these means, the old Edge will effectively disappear from all entry points in the UI, but it will still be there and so will the EdgeHTML engine, which is still used by UWP apps and more. I think in the long run that one will be replaced by the new engine as well but that is still some ways off - see the documentation for the new Chromium-based WebView 2:
"Developer preview is available for Win32 C++ on Windows 10, Windows 8.1, Windows 8, and Windows 7. In the future, we plan to support WebView2 on .NET, and XAML."
From https://docs.microsoft.com/en-us/microsoft-edge/hosting/webview2
adrianghc wrote:
The way I understood it, beginning January 15 the new Edge will start to be pushed out to users automatically. If the new Edge is installed through these means, the old Edge will effectively disappear from all entry points in the UI, but it will still be there and so will the EdgeHTML engine, which is still used by UWP apps and more. I think in the long run that one will be replaced by the new engine as well but that is still some ways off - see the documentation for the new Chromium-based WebView 2:
"Developer preview is available for Win32 C++ on Windows 10, Windows 8.1, Windows 8, and Windows 7. In the future, we plan to support WebView2 on .NET, and XAML."
From https://docs.microsoft.com/en-us/microsoft-edge/hosting/webview2Yeah the Webview was also the reason why they have been holding off the plan to roll out SETS to Windows 10, because they wanted to use the new Webview 2 based on Chromium for the SETS.
at least that's what I had read about it.
https://www.youtube.com/watch?v=3lEjuU-XFHg
