OS HTML renderer


So with this new Credge thing, what does this mean for web browser controls in apps and the state of updates for the underlying html renderer within the OS? Will that continue to use an increasingly outdated EdgeHTML, will they ship a new WebKit with each OS update or will they try update the renderer every week?

Either way, what does this mean for developers who have relied on specific compatibility in their web browser controls in Win32, .NET and UWP? Surely neither swapping rendering engines nor dealing with an outdated, ignored one is really satisfactory.

Comments (3)

3 responses to “OS HTML renderer”

  1. skane2600

    Can we assume that these controls are IE-based and not Edge-based? I doubt many devs have started using those lately and if they are, in fact, used primarily in legacy applications and they are still supported I don't see a problem. I don't see any real advantage in rewriting legacy programs to use a new Credge-based renderer or control if it's even possible.

  2. lvthunder

    UWP certainly used EdgeHTML. The rest probably use the IE engine would be my guess. I think over time they will make UWP use the New Edge engine via translation if they even need that.

  3. sevenacids

    From what I heard, the current XAML WebView control in UWP will stay untouched and remain on EdgeHTML (for compatibility purposes), and a new control will be introduced that uses the Chromium-based engine.

    The WPF and Windows Forms controls are outdated for a very long time as they are still based on MSHTML. But you could use XAML islands to reuse the UWP WebView control in WPF and Windows Forms. This way, you'll get at least EdgeHTML. There is also Awesomium, which provides third-party Chromium-based web view controls for WPF and Windows Forms.

    As for the update cycle, I assume that new UWP control libraries, including Chromium-based Edge web controls, will be distributed via package managers like NuGet and decoupled from the base OS. This is already the case with the UWP community toolkit, for example.