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).
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
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.
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?
Use the below link to open Feedback hub app and up vote the issue
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.