Internet Explorer Doesn't Render Correctly When Embedded As WebBrowser Control - by BetterToday

Status : 

  By Design<br /><br />
		The product team believes this item works according to its intended design.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

ID 571671 Comments
Status Closed Workarounds
Type Bug Repros 2
Opened 6/29/2010 8:13:31 AM
Access Restriction Public


For one of my Aeronautic clients I am evaluating the deployment of Internet Explorer within a Java application.

We were quite startled to see that Internet Explorer doesn't render HTML correctly when embedded as ActiveX control into an application.

I could reproduce the problem by embedding Internet Explorer into a .NET application using the WebBrowser control coming with Visual Studio 2010. Even here Internet Explorer messes up table layout and element positioning.

Please refer to attached samples to reproduce the problem.

We are still investigating on deploying Internet Explorer or not. So a quick response would be very welcome.

Axel Dahmen
Sign in to post a comment.
Posted by Microsoft on 7/22/2010 at 3:26 PM
As with all feature requests, we will resolve this as by design. However, your feedback has been noted.

if you haven't found them already, you can read these links for more information about this area.

Best regards,

The IE Team
Posted by Microsoft on 7/21/2010 at 6:15 PM
Thank you for your feedback. We will take your feedback into consideration in our ongoing process of improving Internet Explorer.

Best regards,

The IE Team
Posted by BetterToday on 7/3/2010 at 12:59 AM
I now learned that the above mentioned problem happens due to some "extraordinary functionality" hidden in some registry keys whose name begin with "FeatureControl"...

Who came up with this??

I strongly suggest to add reasonable and publicly visible properties to the Internet Explorer WebBrowser control, providing a well defined interface to programmers so they don't need to guess around what the IE WebBrowser control "might" be able to do and so they won't need to fiddle around somewhere in the registry (unbelievable) to do their job.

Using a couple of cryptical and hardly known registry entries requiring programmers to fiddle around in the Registry is more a hack and bad programming style than being a professional approach. I very well remember using Peek and Poke commands to achive my goals back in 1982. And although it was interesting to explore hidden features back when I was jung I don't believe there is room for this programming style now in a professional environment.

Axel Dahmen
Posted by BetterToday on 7/1/2010 at 11:37 AM
Please refer to here for a discussion on this issue: