Will the IE9 WebBrowser Control Support all of IE9 s features including SVG

Question

I recently upgraded to IE9-beta  Now  In my  Net  3 5  WinForm application I want to use WebBrowser control    So my question is  whether the WebBrowser control will exhibit all properties and functions of IE9    My concern is  I want to render some SVG graphics on it

User · Answer

WebBrowser control will use whatever version of IE you have installed, but for compatibility reasons it will render pages in IE7 Standards mode by default.

If you want to take advantage of new IE9 features, you should add the meta tag <meta http-equiv="X-UA-Compatible" content="IE=9" > inside the <head> tag of your HTML page.

This meta tag must be added before any links to CSS, JavaScript files etc that are also in your <head> to work properly though (only other <meta> tags or the <title> tag can come before it).

An alternative is to add a registry entry to:

HKLM > SOFTWARE > Microsoft > Internet Explorer > Main > FeatureControl > FEATURE_BROWSER_EMULATION

And in there add 'myApplicationName.exe' with value '9000' to force the WebBrowser control to display pages in IE9 mode. Though there are other values you can use too too, note that these docs aren't entirely accurate as it does not seem possible to get a page to render in IE 8 mode whatever value you use.

Adding the registry key to the same path in HKCU instead of HKLM will also work - this is useful as writing to HKLM requires admin privileges where as HKCU does not.

User · Answer

I had the same problem  and the registry answers here didn t work   I had a browser control in new version of my program that worked fine on XP  failed in Windows 7  64 bit   The old version worked on both XP and Windows 7   The webpage displayed in the browser uses some strange plugin for showing old SVG maps  I think its a Java applet    Turns out the problem is related to DEP protection in Windows 7     Old versions of dotnet 2 didn t set the DEP required flag in the exe  but from dotnet 2  SP 1 onwards it did  yep  the compiling behaviour and hence runtime behaviour of exe changed depending on which machine you compiled on  nice          It is documented on a MSDN blog NXCOMPAT and the C  compiler  To quote   This will undoubtedly surprise a few developers   download a framework service pack  recompile  run your app  and you re now getting IP ON HEAP exceptions   Adding the following to the post build in Visual Studio  turns DEP off for the exe  and everything works as expected   all    DevEnvDir    tools vsvars32 bat  editbin exe  NXCOMPAT NO    TargetPath      Editbin documentation Dumpbin  headers will display the DEP setting on a exe

User · Answer

Just to be complete     For 32 bit OS you must add a registry entry to   HKEY LOCAL MACHINE SOFTWARE Microsoft Internet Explorer MAIN FeatureControl FEATURE BROWSER EMULATION          OR         For 64 bit OS you must add a registry entry to   HKEY LOCAL MACHINE SOFTWARE Wow6432Node Microsoft Internet Explorer MAIN FeatureControl FEATURE BROWSER EMULATION   This entry must be a DWORD  with the name being the name of your executable  that hosts the Webbrowser control  i e    myappname exe  DON T USE  Contoso exe  as in the MSDN web page   it s just a placeholder name   Then give it a DWORD value  according to the table on   http   msdn microsoft com en-us library ee330730 v vs 85  aspx browser emulation  I changed to 11001 decimal or 0x2AF9 hex ---  IE 11 EMULATION  since that isn t the DEFAULT value  if you have IE 11 installed -- or whatever version    That MSDN article contains notes on several other Registry changes that affects Internet Explorer web browser behavior

User · Answer

I came to this solution and it did not worked for me  Because I was using 64bit I had to replace the registry   HKEY LOCAL MACHINE SOFTWARE Wow6432Node Microsoft Internet Explorer MAIN FeatureControl FEATURE BROWSER EMULATION   Instead of the one that everyone talks about    HKEY LOCAL MACHINE SOFTWARE Microsoft Internet Explorer Main FeatureControl FEATURE BROWSER EMULATION

User · Answer

I know this thread is old and there are already comprehensive answers   Just in case you don t know this     lt meta http-equiv  X-UA-Compatible  content  IE edge   gt   You don t have to hardcode IE version number as   lt meta http-equiv  X-UA-Compatible  content  IE 9   gt

User · Answer

Thank goodness I found this   The following is extremely important    lt meta http-equiv  X-UA-Compatible  content  IE 9   gt    Without this  none of the reports I d been generating would work post IE9 install despite having worked great in IE8   They would show up properly in a web browser control  but there would be missing letters  jacked up white space  etc  when I called  Print     They were just basic HTML that should be capable of being rendered even in Mosaic   heh  Not sure why the IE7 compatibility mode was going haywire   Notably  you could  Print   the same page 5 times and have it be missing different letters each time   It would even carry over into PDF output  so it s definitely the browser

User · Answer

Yes  WebBrowser control uses whatever version of IE you have installed  This means of course that if you run your application on a machine with IE 8 then the IE 9 features you depend on will not be available

User · Answer

The IE9  version  of the WebBrowser control  like the IE8 version  is actually several browsers in one  Unlike the IE8 version  you do have a little more control over the rendering mode inside the page by changing the doctype  Of course  to change the browser mode you have to set your registry like the earlier answer  Here is a reg file fragment for FEATURE BROWSER EMULATION   Windows Registry Editor Version 5 00   HKEY LOCAL MACHINE SOFTWARE Microsoft Internet Explorer Main FeatureControl FEATURE BROWSER EMULATION   contoso exe  dword 00002328   Here is the complete set of codes    9999  0x270F  - Internet Explorer 9  Webpages are displayed in IE9 Standards mode  regardless of the  DOCTYPE directive   9000  0x2328  - Internet Explorer 9  Webpages containing standards-based  DOCTYPE directives are displayed in IE9 mode     8888  0x22B8  -Webpages are displayed in IE8 Standards mode  regardless of the  DOCTYPE directive  8000  0x1F40  - Webpages containing standards-based  DOCTYPE directives are displayed in IE8 mode  7000  0x1B58  - Webpages containing standards-based  DOCTYPE directives are displayed in IE7 Standards mode    The full docs   http   msdn microsoft com en-us library ee330730 28VS 85 29 aspx browser emulation

User · Answer

I totally agree with the solution provided  but I think a little clarification is important I think  might be necessary   For each process  read also  vshost exe  yourWinformApplication exe svchost  or the name of your application exe  that will need to add a DWORD with the value provided  in my case I leave 9000  in decimal  in application name and running smoothly and error-free script   the most common mistake is to believe that it is necessary to add  contoso exe  AS IS and think it all work

User · Answer

Regarding whitehawk s accepted answer   I am just trying to add a bit hands on experience  Was just trying to add a comments  but SO complains it s too long   Basically  without IE 9 installed  the registry switch FEATURE BROWSER EMULATION won t work AT ALL   For example  my own experience today I was trying to get the  net webcontrol to work with IE10 mode because one html I am trying to render won t work with  netControl under VS2012  and not even work when I load the html to IE8 directly  still css won t render properly even after I say allow blocked content   But I have tested the same html ok with IE10 on a friend s win 8 machine  That s why I am trying to set the  net webControl to IE 10 mode but just keeps failing     Now I figured this is bcos my win 7 machine only have IE8 installed  so regardless which value I set to the FEATURE BROWSER EMULATION switch value to IE9  IE10 IE11   it just won t work AT ALL    Then I downloaded and installed IE 10 on my win 7 machine  Still it won t work  then I added the FEATURE BROWSER EMULATION  it started working     Also I noticed regardless which value I set   even set it to value 0 by default  the webControl is still using IE 10 mode which still works for me   So to summarise  If you have IE X installed but you want your  Net webControl to work under IE  X N  N 0 modo  TWO things you need to do    Go to MS website  amp  download and install IE  X N  on your machine  you will need to reboot  after installation  apply whitehawk s answer    Basically  To control the value of this feature by using the registry  add the name of your executable file to the following setting and set the value to match the desired setting   HKEY LOCAL MACHINE  or HKEY CURRENT USER     SOFTWARE       Microsoft          Internet Explorer             Main                FeatureControl                   FEATURE BROWSER EMULATION                      contoso exe    DWORD  00009000   Windows Internet Explorer 8 and later  The FEATURE BROWSER EMULATION feature defines the default emulation mode for Internet Explorer and supports the following values   Value   Description   11001  0x2AF9    Internet Explorer 11  Webpages are displayed in IE11 edge mode  regardless of the  DOCTYPE directive   11000  0x2AF8    IE11  Webpages containing standards-based  DOCTYPE directives are displayed in IE11 edge mode  Default value for IE11   10001  0x2711    Internet Explorer 10  Webpages are displayed in IE10 Standards mode  regardless of the  DOCTYPE directive   10000  0x02710   Internet Explorer 10  Webpages containing standards-based  DOCTYPE directives are displayed in IE10 Standards mode  Default value for Internet Explorer 10   9999  0x270F     Windows Internet Explorer 9  Webpages are displayed in IE9 Standards mode  regardless of the  DOCTYPE directive   9000  0x2328     Internet Explorer 9  Webpages containing standards-based  DOCTYPE directives are displayed in IE9 mode  Default value for Internet Explorer 9   Important  In Internet Explorer 10  Webpages containing standards-based  DOCTYPE directives are displayed in IE10 Standards mode   8888  0x22B8     Webpages are displayed in IE8 Standards mode  regardless of the  DOCTYPE directive   8000  0x1F40     Webpages containing standards-based  DOCTYPE directives are displayed in IE8 mode  Default value for Internet Explorer 8 Important  In Internet Explorer 10  Webpages containing standards-based  DOCTYPE directives are displayed in IE10 Standards mode   7000  0x1B58     Webpages containing standards-based  DOCTYPE directives are displayed in IE7 Standards mode  Default value for applications hosting the WebBrowser Control    Full ref here

User · Answer

A note about 64bit Windows which seems to trip up a few folks  If your app is running under 64bit Windows  you likely have to set the DWORD under  HKLM SOFTWARE Wow6432Node Microsoft Internet Explorer Main FeatureControl FEATURE BROWSER EMULATION  instead

User · Answer

I liked the  C   code in the following which sets the registry settings for your app  Not sure if it will cut it after installation though if permissions are required  For me it solved an issue with WebSocket not being available inside a WebBrowser control in WPF   C  webbrowser Ajax call

[c#] Will the IE9 WebBrowser Control Support all of IE9's features, including SVG?

Examples related to c#

Examples related to .net-3.5

Examples related to browser

Examples related to webbrowser-control

Examples related to internet-explorer-9