HI, I don't know if this is a dead issue or if this will help but it is some thing that we have noticed here. If you remove the initial <head> tag from your template and allow TIDY to fix afterward you get different results. The comment that they inject for the CMS version and page number is removed.... as well as the <meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7,IE=EmulateIE9,IE=EmulateIE10" /> They seem to like attaching processes to the presence of the <head> tag. Wish I could help more but that is all I can offer. Hope it is useful to someone. Chris H.
On Tuesday, December 10, 2013 5:56:36 PM UTC-5, Morgan Ritchings wrote: > Hi All, > > The challenge i have and am looking to share with my fellow > reddoters/wsmers is as follows: How do you get ie8 to render as ie8 > standards mode in Smartedit (targeting V11.1)? > > Background: > The cms forces IE8 in to ie7 compatibility mode by default in smartedit. > > Restrictions: > No alternate browsers or later IE versions allowed - must be ie8. > IIS and Web.config changes are ok. > CMS Template hackery is ok - but my investigations to date don't beleive > this will help. See below. > > Here's the notes on my investigation to date: > > Compatibility mode is defined in a server side http header > programmatically for the smartedit.aspx parent frame/page. the > compatibility meta tag isn't actually set on the smartedit parent frame and > you can't hack it out from the aspx page.As the template code is loaded > from a child frame it can't influence the rendering mode. Unless there's a > magic setting I'm missing then its going to have to be patched out of the > application code (the force ie7 mode only relates to ie9 oddly enough) > > http header notes: > 1. Http Header (injected within the application code - i'm assuming this > hangs off the "force ie7 mode" in the latest versions) > 2. Http Header (specified by web.config - you can change this but option 1 > prefixes your changes which prevents it making a difference) > 3. Smartedit.aspx (doesn't specify compatibility meta tag - can't hack > this to add meta compatiblity tag but given the item 1 above the syntax > will bypass the meta tag even if you could embed it) > 4. Template code in child frame (can strip any meta tags or reaplce them > but won't be evaluated as it is in a child frame) > > > - Morgan > -- You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to reddot-cms-users+unsubscr...@googlegroups.com. To post to this group, send email to reddot-cms-users@googlegroups.com. Visit this group at http://groups.google.com/group/reddot-cms-users. For more options, visit https://groups.google.com/d/optout.
