locked
IE10 ignoring directives to run in IE9 mode RRS feed

  • General discussion

  • We are running a SharePoint 2013 Web Part application and IE 10 is ignoring the settings. 

    We want to run IE10 in compatibility mode using IE9 standards. 

    We have successfully set the page meta tags to point to IE 9 emulation mode, but IE 10 is ignoring these settings

    With Dev tools open (F12) the menu bar shows Browser Mode: IE 10 and Document Mode: Standards in spite of the Web Page HTML showing the following:

    See bolded text in this capture from the IE Development tool

    <!-- saved from url=(0050)http://w28r2ent207/Cognos%20BI/vs2005NavRptVw.aspx -->
    <!-- Generated by F12 developer tools. This might not be an accurate representation of the original source file -->
    <html lang="en-US" dir="ltr"><head><script type="text/javascript">
    //<![CDATA[
    window.ComponentArt_Atlas=1;window.ComponentArt_Fw35=1;
    //]]>
    </script>
    <script type="text/javascript">
    //<![CDATA[
    window.ComponentArt_Atlas=1;window.ComponentArt_Fw35=1;
    //]]>
    </script>
    <meta name="GENERATOR" content="Microsoft SharePoint"><meta http-equiv="Content-type" content="text/html; charset=utf-8"><meta http-equiv="X-UA-Compatible" content="IE=EmulateIE9"><meta http-equiv="Expires" content="0"><meta name="msapplication-TileImage" content="/_layouts/15/images/SharePointMetroAppTile.png"><meta name="msapplication-TileColor" content="#0072C6"><title>

    Neil Thomson

    Friday, September 13, 2013 2:26 AM

All replies

  • Hi Neil,

    f12>Console tab... refresh the page.... the console of the developer tool will list ALL x-ua compatibility attempts... including server headers or domains in the MS Compatibility view lists.

    this

    <!-- saved from url=(0050)http://w28r2ent207/Cognos%20BI/vs2005NavRptVw.aspx -->

    Indicates that it may not be a html file, but rather a mht?

    Regards.


    Rob^_^

    Friday, September 13, 2013 4:27 AM
  • Rob,

    I'm not seeing anything I would describe as compatibility attempts. Example of the developer tool console when showing the web page with compatibility set to on for the site:

    HTML1201: w28r2ent207 is a website you've added to Compatibility View.
    vs2005NavRptVw.aspx
    SEC7115: :visited and :link styles can only differ by color. Some styles were not applied to :visited.
    vs2005NavRptVw.aspx
    SCRIPT438: Object doesn't support property or method 'querySelector'
    sp.core.js, line 2 character 18188
    SCRIPT438: Object doesn't support property or method 'querySelector'
    init.js, line 1 character 84618

    Given this is a SharePoint 2013 app, I get the above list of warnings and errors on standard SP2013 pages without our web parts...


    Neil Thomson


    Friday, September 13, 2013 2:23 PM
  • After reading elsewhere that the <meta http-equiv="X-UA-Compatible" content="IE=EmulateIE9"> statement really has to be early, if not first in the header or it will be ignored. 

    If the two lines:

    <meta http-equiv="Content-type"  ontent="text/html; charset=utf-8">
    <meta http-equiv="X-UA-Compatible" content="IE=EmulateIE9">

    are to the front of the header, the Compatible content is picked up, if not, then it's ignored.


    Neil Thomson

    Friday, September 13, 2013 6:51 PM