Note that there are some explanatory texts on larger screens.

plurals
  1. POForce IE8 not to use compatibility mode, using MetaData in Theme not working
    primarykey
    data
    text
    <p>As my question Title already tells I have problems forcing the IE8 not to use the compatibility mode. </p> <p>I found two solutions on the web one from <a href="http://xpagesblog.com/XPagesHome.nsf/Entry.xsp?documentId=1CA7F24C230675CE852578CB00667375" rel="nofollow noreferrer">Michael Gollmick</a>, wich adds this Code to the beforeRenderResponse:</p> <pre><code>if (context.getUserAgent().isIE()) { var response = facesContext.getExternalContext().getResponse(); response.setHeader("X-UA-Compatible", "IE=8"); } </code></pre> <p>This solution works fine the Compatibility mode Button in the Browser disapears and the Page looks like it should. B</p> <p>ut I don't want to add this Code to every XPage, so I tried the solution from Per <a href="https://stackoverflow.com/questions/9489677/alignment-problems-in-the-extension-library-application-layout-placebar-in-ie-bu">Henrik Lausten</a> to add MetaData to my Theme:</p> <pre><code>&lt;resources&gt; &lt;metaData&gt; &lt;httpEquiv&gt;X-UA-Compatible&lt;/httpEquiv&gt; &lt;content&gt;IE=8&lt;/content&gt; &lt;/metaData&gt; &lt;/resources&gt; </code></pre> <p>But it seems that this MetaData in the Theme has no efect. When taking a look at the HTML source Code I found the Meta tag in the header of the sourceCode but IE8 seems just to ignore it.</p> <pre><code>&lt;meta content="IE=8" http-equiv="X-UA-Compatible"&gt; </code></pre> <p>So how can I get the MetaData from the Theme working? Or maby any other solution to automatical add the onRenderResponse Code to every XPage.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload