We solved this issue. We actually had this meta tag in our header:

 <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1" />

but it did not work. Turns our that this is a known issue in the HTML5 
boilerplate that our front-end is based on and we had to move the 
conditional comments around:
https://github.com/h5bp/html5-boilerplate/issues/378

So, for the time being we have to add a meta tag like the above to your 
foundation templates if you don't want IE to behave like IE7 (and actually 
slow down quite a bit too). 

OpenText confirmed that there is a related feature request for this 
(WSGREQ-780) - about time that the UI get's update... 

Heiko


On Monday, 10 September 2012 15:41:24 UTC+10, Christoph Straßer wrote:
>
> It should work to add something like the following to to the template of 
> your masterpage-contentclass:
> <meta http-equiv="x-ua-compatible" content="IE=9; IE=8">
>
> I hope, OpenText moves the old-UI-components to 
> state-of-the-art-technology within the next years, so they do not need to 
> set the x-ua-header any more.
>
> Kind regards,
>
> Christoph
>
> Am Samstag, 8. September 2012 05:00:58 UTC+2 schrieb heiko:
>>
>> Yes, it seems like OpenText is supporting IE8 and IE9 by simply forcing 
>> them to behave like IE7. This also seems to slow down the browsers quite a 
>> bit. Using a different browser for SmartEdit is an option of course - but I 
>> don't like the idea of telling a client that they have to switch browsers 
>> depending on what functionality they want to use in the CMS... 
>>
>> I've also pinged OpenText support on the possibility of changing the 
>> header value - will keep you posted. 
>>
>> Cheers
>> Heiko 
>>
>>
>> On Friday, 7 September 2012 17:57:03 UTC+10, ChrisJ wrote:
>>>
>>> That's interesting, I didn't realise that Reddot v11 tries to force IE7 
>>> mode in the headers.  We have problems with IE7 bugs on our site confusing 
>>> users in SmartEdit, but we're only on Reddot v10, so I'd have hoped that 
>>> browser support would've moved on in the next version.  They can't keep 
>>> building the Management Server with IE7 as the reference browser, that's 
>>> just not sustainable - it wont be long before MS stop being backwards 
>>> compatible to that level of rendering when their making such good strides 
>>> with IE9 & IE10.
>>>
>>> Sorry can't help you here, apart from just saying you could try and use 
>>> another browsers, Chrome or Firefox, which SmartEdit seems to be OK with?
>>>
>>> Cheers,
>>> Chris.
>>>
>>> On 6 September 2012 23:46, heiko <[email protected]> wrote:
>>>
>>>> Hi All, 
>>>>
>>>> I noticed that v11 of the CMS adds a HTTP header to all responses, that 
>>>> forces IE to display all pages in IE7 mode (IE=EmulateIE7). We're 
>>>> currently 
>>>> building a project that no longer fully supports IE7 - and the header 
>>>> breaks the pages in SmartEdit and Preview (content authors are using IE8 
>>>> and IE9). What is your experience with setting the HTTP header value in 
>>>> IIS 
>>>> to IE=EmulateIE8? Does this affect any of the CMS functionality? 
>>>> Or is there another way to not force IE in IE7 mode for SmartEdit? A 
>>>> meta tag does not work, the HTTP header seems to override the meta tag. 
>>>>
>>>> Cheers
>>>> H
>>>>
>>>> -- 
>>>> You received this message because you are subscribed to the Google 
>>>> Groups "RedDot CMS Users" group.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msg/reddot-cms-users/-/BGhjBxpDE70J.
>>>> To post to this group, send email to [email protected].
>>>> To unsubscribe from this group, send email to 
>>>> [email protected].
>>>> For more options, visit this group at 
>>>> http://groups.google.com/group/reddot-cms-users?hl=en.
>>>>
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"RedDot CMS Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/reddot-cms-users/-/sMBGCclfdbEJ.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/reddot-cms-users?hl=en.

Reply via email to