none
FEATURE_BROWSER_EMULATION code for IE11 RRS feed

Answers

All replies

  • I'm using WebBrowser control and I use FEATURE_BROWSER_EMULATION to define the emulation mode. In MSDN page I do not find code for IE11 version



    http://blogs.msdn.com/b/ieinternals/archive/2013/09/21/internet-explorer-11-user-agent-string-ua-string-sniffing-compatibility-with-gecko-webkit.aspx

    (Microsoft Search for
        IE11 document standards site:blogs.msdn.com
    )

    A similar search for the term that you are interested in only yields older documents.

    Modern.IE has some links which I think also reinforces the idea that standards are now more important to IE than compatibility and extensibility.

    http://www.modern.ie/en-US/category/whats-new

     



    Robert Aldwinckle
    ---

    Tuesday, November 5, 2013 5:53 AM
  • My problem is different.

    If you use WebBrowser control inside a WPF or Windows application by default it uses IE7 emulation. The only way to tell the control to use different emulation is through Registry Key, but since the value for IE 11 is not available in MSDN, I'm not able to use IE 11 features with WebBrowser control, and it uses IE 10 emulation, so I'd like that MSDN page to be updated with codes for IE 11 :).

    Gian Maria.


    Ricci Gian Maria. (http://www.codewrecks.com)

    Tuesday, November 12, 2013 4:30 PM
  • I am having the same issue. Mine is a WinForm application and I need to force WebBrowserControl to use IE 11 rendering engine. I too am looking for the same registry setting. Following article is NOT updated for IE 11:

    http://msdn.microsoft.com/en-us/library/ee330730%28v=vs.85%29.aspx#browser_emulation


    • Edited by Harit Singh Tuesday, November 12, 2013 4:46 PM
    Tuesday, November 12, 2013 4:45 PM
  • The only way to tell the control to use different emulation is through Registry Key

    I thought that is what  IECompatData.xml  could do (provided you have a distinct host name, I suppose)?  Is that file not accessed by your program?  Use ProcMon to check.  Also, just because something isn't documented doesn't mean that you can't use it.  Again, I would try using ProcMon to check.  E.g. Filter with RegQueryValue perhaps.


    Robert Aldwinckle
    ---

    Tuesday, November 12, 2013 6:28 PM
  • I do not think that IECompatData.xml is what I need, I do not care about IE11, I need to force the WebBrowser control in mine application written in .NET to render as IE11, and as far as I know the FEATURE_BROWSER_EMULATION flag is the only solution.

     IECompatData.xml is used to specify hosts that you want to access in compatibility mode, but I do not think it is used by the WebBrowser control. The symptom is simple, create a Windows Forms application, drop a WebBrowser control and then simply do a google search and you got this, because actually the browser control is using Compatibility View.

    


    Ricci Gian Maria. (http://www.codewrecks.com)


    Wednesday, November 13, 2013 8:09 AM
  • The symptom is simple, create a Windows Forms application, drop a WebBrowser control and then simply do a google search and you got this, because actually the browser control is using Compatibility View.


    I don't have a Windows Forms application to use to do my ProcMon test but you do.  So, if you started yours with ProcMon running you could know whether IECompatData.xml could be a factor or not much more easily (and presumably with more interest in the result) than I could.



    Robert Aldwinckle
    ---

    Wednesday, November 13, 2013 2:36 PM
  • I've checked and no access to IECompatData.xml is done by the WebBrowserControl as I suspected.

    I wonder why MSDN documentation is not updated with code for IE11 and it is still stuck to IE10, this is a Windows 8.1 blocking adoption for one of my customer :(.

    Gian Maria.


    Ricci Gian Maria. (http://www.codewrecks.com)

    Wednesday, November 13, 2013 3:12 PM
  • I've asked the IE Documentation writer to update the documentation for FEATURE_BROWSER_EMULATION.
    Wednesday, November 13, 2013 9:25 PM
  • http://msdn.microsoft.com/en-us/library/ee330730(v=vs.85).aspx shows the existing values. I've confirmed that 11000 (decimal) or (0x2710 hex) works to force the control into IE11 mode.
    Thursday, November 14, 2013 7:38 PM
  • Thank you for your response. Seems like that 11000 is the decimal value for displaying webpages containing standards-based !DOCTYPE directives in IE 11. What value can be used to force IE 11 regardless of the !DOCTYPE directive (in case of IE 10, it's 10001 (0x2711))

    Thursday, November 14, 2013 8:04 PM
  • Thanks to you for the answer, actually the 11000 is enough for me, but knowing also the value to force IE 11 regardless !DOCTYPE (as requested by Harit) could also be useful (but not necessary for me).

    Thanks.

    Gian Maria.


    Ricci Gian Maria. (http://www.codewrecks.com)

    Friday, November 15, 2013 10:35 AM
  • As far as I can tell in my tests, none of the "force standards" values behave differently when loading a HTML page that doesn't contain a doctype-- they ALL behave the same way as the default "use mode <n>" values. I'm following up with the IE engineering team.
    Friday, November 15, 2013 7:54 PM
  • Not to be picky by 0x2710 is 10000, not 11000. For 11000 that would be 0x2af8.

    R.D. Holland

    • Proposed as answer by Zaren1 Tuesday, July 31, 2018 9:20 PM
    Tuesday, March 22, 2016 7:07 PM
  • Not to be picky by 0x2710 is 10000, not 11000. For 11000 that would be 0x2af8.

    R.D. Holland


    Value Description
    11001 (0x2AF9)   Internet Explorer 11. Webpages are displayed in IE11 edge mode, regardless of the declared !DOCTYPE directive. Failing to declare a !DOCTYPE directive causes the page to load in Quirks.
    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.
    Tuesday, July 31, 2018 9:21 PM
  • Even if I enter 11001 (0x2AF9) the WebBrowser control is running differently to standalone IE11 application.

    Unfortunately the JS pointer events are not processed.

    What can be done to make the pointer events work in WebBrowser control?


    René Rössler


    • Edited by R.Roessler Friday, July 19, 2019 7:44 AM
    Friday, July 19, 2019 7:13 AM