Hi everyone,
I've got a requirement to force a Cognos generated report to default to IE11 format, rather than the standard IE5 format. The "View Source" option shows the following meta tag for the report:
"<meta http-equiv="X-UA-Compatible" content="IE=5"/>"
How can I change this so that it shows "IE=11" at the end? There are some template files that can be adjusted to do this, however this is a global setting and will affect ALL generated reports, whereas it is only one particular report that needs this setting.
Any suggestions?
I see no such meta tags on my reports - IE, Firefox, or Chrome. :-\
Knowing our server admin likes to keep configurations as out-of-the-box as he can, I am going to go out on a limb and suggest that you already have some customization that is forcing the meta tag in the first place. I know this can be configured site-wide in IIS, so if you are on Windows I would look there first.
That's a weird requirement.
Firstly, I don't think IE=11 is acceptable. I think one ought to be using IE=edge. But more importantly, the X-UA-Compatible meta tag allows web authors to choose what version of Internet Explorer the page should be rendered as. This affects whether the page is rendered in quirks mode for IE7+, so it affects compatibility. The tag is there for a reason. Changing the tag, even if it were possible (I don't think it is, by the way, not without editing system files for the entire Cognos environment) won't make your report compatible with IE10 or IE11 not in comp. mode; rather, it will fool your browser to think that it is, thus rendering the page wrong.
But the main reason I find such a requirement strange is that it isn't something customers usually would ask for ("So, you know, make the colours a bit more...blue-y. Oh, and make the X-UA meta tag IE11, will you?").
A few years ago I had a neighbour who came by asking for a drill, because he was putting together a table. That sounded strange, so I started asking. He said that he doesn't have a screwdriver, so he is hammering the screws in, but the holes aren't big enough so he needs a drill to smooth them over. I lent him a screwdriver. Just goes to show that sometimes we are so focused on doing things one way, we overlook something, and maybe if we told the whole story, we could find an easier way. So, why is it that you or your customer feel compelled to change the page compatibility of this report?
Hi Nimrod,
The Customer wanted to have a Twitter feed placed on this report and Twitter have stated that this feature will not be compatible with browsers older than IE8, which is why they were looking into this. Aside from the template files that can be edited (which would make this change global), there wasn't any other way of adding in the meta tag.
They've accepted that this can only be done globally if needed and I think they're going to explore other options, rather than trying to edit tags in one report.
Thanks.
This has nothing to do with the meta tag. You can add a Twitter feed to the report in an iframe.
I do not have a Twitter logon, so maybe that makes a difference. But, I just tried using this in an HTML Item to test the feed and sadly, Twitter has iframe-busting code.
<iframe src="http://twitter.com/linustorvalds"></iframe>
https://blog.twitter.com/2012/embedded-timelines-howto