SOLVED: xsp.properties Meta tag?

HCL Domino Domino Forum
1

I’m wondering if there’s a better way of trying to force IE=8 mode for an XPages application. I was hoping to be able to just add something to the xsp.properties file but I don’t know what to add to it achieve this:

What I’ve done in the meantime is add a meta tag resource to each individual XPage as per Paul Hannan’s post: http://www-10.lotus.com/ldd/nd85forum.nsf/5f27803bba85d8e285256bf10054620d/c96823ba78d345a58525757b003e554c?OpenDocument

While I do seem to get a tag when I view the source:

it doesn’t appear to stop someone from manually triggering the compatibility mode setting, which I find disappointing.

Anyone know how I can set this meta tag via the xsp.properties file?

And, does anyone know if you can programmatically disable that compatibility mode button?

Thanks for any suggestions/help,

Judy.

2

Subject: Still hoping for help …

Actually, I’m not sure using the xp:meta tag resource on each XPage is even working. It certainly isn’t forcing IE=8 mode.

According to the MSDN site:

The X-UA-compatible header is not case sensitive; however, it must appear in the Web page’s header (the HEAD section) before all other elements, except for the title element and other meta elements.

And, what I see when I view source on an XPage that uses the tag resource is:

… (etc.) …

… (etc.) …

3

Subject: Still hoping for help

Hello Judy,

you can add the meta tag by including it in your theme. That way, you don’t have to add it to each individual XPage and it will be included in the tag:

<metaData content="IE=edge" httpEquiv="X-UA-Compatible" />

You can even have it added conditionally, meaning, it will only be added when the browser matches the browser version you define:

<metaData rendered="#{javascript:context.getUserAgent().isIE(7,9)}" content="IE=edge" httpEquiv="X-UA-Compatible" />

isIE(7,9) provides the range of IE versions to which this meta tag will be added to the tag.

Hope this helps.

Daniel