![]() But as these features have become common in browsers, the tide is slowly turning and more and more JavaScript libraries are now embracing the new JavaScript features which Internet Explorer has never and will never support. This used to be no big deal because until very recently even most Chromium browsers hadn't implemented many ES2015 features. NET Interop and the old control actually works just fine for both of these scenarios.īut, where the old control starts failing is for content that uses modern JavaScript that is ES2015 or newer which the IE JavaScript engine doesn't support. Both of these web pages/applications are fairly complex, and use JavaScript to. The WebBrowser control in WPF and WinForms is a built in control, and although it's very old and based on Internet Explorer, it can render most HTML 5 content and many relatively modern JavaScript libraries.įor example, in Markdown Monster I use the IE WebBrowser control very effectively to render the JavaScript based editor and Web preview browsers and that just fine with excellent performance for example. The old Internet Explorer based Web Browser Control It provides fast, modern rendering that's (optionally) always updated to the latest Chromium features, which is the browser engine that most mainstream browsers now all use for HTML rendering - the big exception being FireFox.īefore we dive into the WebView, first a little history on where we are coming from. So coming from a WebBrowser control, the WebView2 control seems like a shoo-in especially for new applications. The original WebView control is now obsolete and longer supported. Note that the WebView2 is a very different control than the original WebView control, which existed briefly and was based on the classic Edge engine. Part 2 focuses on interaction with content and. In this installment I'll talk about the control's features, and how to use the control to display content and how to get it installed with your applications. I'll talk about how I went about this integration and some of the challenges I ran into in Part 2. While this process took some effort and finding out a lot about how the control works and what doesn't, overall the end result was very encouraging as I managed - with a bit of effort - to duplicate most of the interop functionality that the preview interface required. NET bits are still in preview, performance and stability are very promising at this point.Īfter some initial experimenting with features and performance, I decided to integrate the WebView2 initially in Markdown Monster as an optional preview browser addin to support Chromium rendering. The WebView2 control is Microsoft's entry in this space and they are throwing their weight behind the Edge Chromium browser with application level features for C++, WinForms and WPF applications. So I was exited to hear that Microsoft was creating a WebView control in tandem with the new Edge Chromium browser that recently was released, even if these developments took a lot longer than originally anticipated. Third party Chromium based controls (like CefSharp) have been available for a while, but for me these complex controls have been a struggle to integrate and operate efficiently and reliably in the past especially in WPF. ![]() ![]() The Microsoft Edge WebView2 control is a new Chromium based Web Browser control that aims to replace the Internet Explorer based WebBrowser control that's commonly used in WPF and WinForms. Part 3 - Real World Integration and Lessons Learned (coming soon).Part 2 - Chromium WebView2 Control and.Part 1 - Taking the new Chromium WebView2 Control for a Spin in.
0 Comments
Leave a Reply. |