12-01-2019 08:10 PM
"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.
12-02-2019 02:59 AM
12-02-2019 04:50 AM
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."
Yeah 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.
12-02-2019 08:25 AM
12-03-2019 04:36 AM
12-03-2019 06:41 AM
At least for me the GPU freeze issue hasn't happened for a good week or two on Beta channel (79.0.309.40). Being stable as it is, I guess I'll keep using this build until Edge goes GA next month.