No Edge version of System.Windows.Forms.WebBrowser Control

Fixed Issue #7749954


Scott B.
Jun 1, 2016
This issue is public.
Found in
  • Microsoft Edge
  • Internet Explorer
Reported by 23 people

Sign in to watch or report this issue.

Steps to reproduce

The WebBrowser control is a commonly used control in desktop application development. There is no way to use the EdgeHTML as the rendering engine for this control (only IE/Trident is available).

Although JavaScript heavy applications (such as Dynamics CRM) work in IE, they perform significantly better in Edge. Making these performance gains available to users of desktop applications would dramatically improve their user experience.


0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Brad E.”

      Changed Status to “By design”

    • Edge would also be a big improvement for WebGL use, because of this IE11 issue:

    • Note that is not only System.Windows.Forms.WebBrowser control (for Windows Forms), but also the System.Windows.Controls.WebBrowser as used in WPF applications.

      Being able to use Edge instead of IE for the WebBrowser control would also be a big improvement for us as IE is not developed further and does not support newest Web standards.

    • We have a product suite which are about to drop support for IE9 and IE10. The .net clients in that product suite have been using web browsers with HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_BROWSER_EMULATION values set to 9999
      The browser client part of our product suite uses javascript which runs in IE11/Edge no problem.
      So we need this problem resolving too

    • Thank you for the feedback. This feedback falls under a feature or design change request. We are currently tracking these types of issues via our ‘Windows Feedback’ application.

         To access Windows Feedback please do the following:
            -  Click on the start button and type Windows Feedback. Cortana will locate the feedback application for you.
            -  Launch the Windows Feedback application
            -  Please search existing feedback. If you find your issue, upvote it.
            -  If you are the first to make this suggestion click on the “Add new feedback” button at the bottom of the window and provide your suggestion.
      Best regards,
      The Microsoft Edge Team

    • Apps for Office performance will also improve, if they would use a Edge-WebView instead of the IE11-WebView

    • This is a big issue and we should all push to get it adopted. There is an item on Windows feedback for this which only has 3 votes.

      Please search windows feedback for “Edge Browser Instead of IE for Web Browser Control” and upvote. Lets see if we can boost it’s priority.

    • i don’t even have Windows Feedback on windows 10 pro. I think it has been renamed Feedback Hub?

    • Why would Microsoft ‘by design’ lock developers into using a browser component that does not support modern features and is no longer under development?

    • I agree with Romann K, the component we’re using MSHTML was discontinued and has not been updated with HTML standards. Programs developed with MSHTML cannot be maintained to keep up with evolving standards and thus become effectively broken.

    • Microsoft Edge Team

      Changed Assigned To to “Charles M.”

      Changed Status from “By design”

    • Thank you all for the feedback. Reactivating this as we are revisiting this issue - please stay tuned for more info in the coming weeks.

    • When I open the Feedback Hub to upvote this issue, I get "Your account doesn’t have access to this feedback". I agree with the other comments on this feature … we need Edge/HTML support for the browser control. IE scores 312 out of 555 (56%) on the test site whereas edge scores 468 out of 555 (84%) . I would like to see Edge HTML5 support be improved too … when compared to Chrome which scores 520 out of 555 (94%)

    • Right now MSHTML is very painful to use. It’s a wrapper that calls into a C++ program and returns instances to "object", throws unmanaged exceptions, hides status codes for failing methods, and can even crash the host process if used incorrectly. There should be an alternative in the .NET framework to manipulate the DOM inside a web browser.

    • Microsoft Edge Team

      Changed Status to “Fixed”

    • Please try the new Edge-based WebView control for Win32/WinForms/WPF apps that was announced today:

    You need to sign in to your Microsoft account to add a comment.

    Sign in