OK. I’m going to get a bit technical here so follow along as best as you can. In the Windows Presentation Foundation (and Windows Forms) there’s a component named WebBrowser. This component shows web pages. The issue here is that it relies on MSHTML (that’s Internet Explorer’s Web Renderer). To make matters worse, if there isn’t a specific tag, it will stick to Version 8 (which doesn’t support modern web technologies). I did add that tag, but relying on IE ain’t gonna be good for long. Thankfully, an update to the Microsoft Community Toolkit (a collection of components for UWP apps) added a few libraries that allow the usage of UWP components to WPF and Windows Forms apps. In my case, I used the WebViewCompatible component. That library switches between MSHTML and EdgeHTML (Microsoft Edge). So, if you are on Windows 10, it uses Edge. If you are on Windows 8.1 or older, you get IE. Now, why didn’t I use a library that provides a different renderer (say, Chromium)? At the moment, it’s a clusterfuck to integrate it to WPF. A library breaks the AnyCPU compilation (compiling the code in the AnyCPU configuration allows the launcher to run in both 32-bit and 64-bit machines using the same executable), another need C++ libraries to ship as well and another hasn’t been updated since. So, for now, this is the best solution until I find a better one.