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.
skane2600
<p>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. </p>