Re: Render IE8 as IE8 in smartedit
The css-issue was fixed with 11.1 HF5. I'll expect this fix is included in 11.2. -- 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/groups/opt_out.
Re: Render IE8 as IE8 in smartedit
Thanks Rustlogic i gave that a go in my original attempts but unfortunately no matter what i did that ie7 emulate header would always be injected. With a bit of research i realised that you can target individual webpages (e..g just the smartedit.aspx) with the location attribute in the web.config. From there you should be able to clear and add whatever headers you want. Unfortunately it appears that the emulate ie7 code was being injected further down the execution of the application and reinjecting it :(. I'm assuming this had to do with the introduction of the force ie7 mode in the project general settings. With OT indicating that there are bugs when running smartedit mode in ie8 and now with 11.2 out and having officially dropped ie7 and ie8 support i think i'm fighting an up hill battle anyway - the end goal was to render ie8 as ie8 and it is to be no more. Sadly the support for IE11 is being delivered via an ie10 compatibility mode - i hope this will be temporary otherwise we might see history repeat itself again in a few years. Another side note is that with ie7 and ie8 now being dropped there is no officially supported browser that will render a css file generated by a content class in smartedit without project specific workarounds. - Morgan On Thursday, 12 December 2013 02:13:03 UTC+11, RustyLogic wrote: Very true but works fine in 11.1 :) On Wednesday, December 11, 2013 3:05:45 PM UTC, Chad Killingsworth wrote: In version 10, the side effect of removing that header is that SmartTree didn't display properly. Chad Killingsworth On Wednesday, December 11, 2013 6:00:18 AM UTC-6, RustyLogic wrote: Been there... In IIS: 1. go to /Sites/Default Web Site/CMS/WebClient 2. Open the HTTP ResponseHeaders 3. Delete the header:X-UA-Compatible: IE=EmulateIE7 4. You can now set it to whatever you like within your projects in the page headers (or do it globally but some of your older projects might still need IE7 to display properly in smartedit) Ta, John On Tuesday, December 10, 2013 10:56:36 PM UTC, 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/groups/opt_out.
Re: Render IE8 as IE8 in smartedit
Been there... In IIS: 1. go to /Sites/Default Web Site/CMS/WebClient 2. Open the HTTP ResponseHeaders 3. Delete the header:X-UA-Compatible: IE=EmulateIE7 4. You can now set it to whatever you like within your projects in the page headers (or do it globally but some of your older projects might still need IE7 to display properly in smartedit) Ta, John On Tuesday, December 10, 2013 10:56:36 PM UTC, 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/groups/opt_out.
Re: Render IE8 as IE8 in smartedit
In version 10, the side effect of removing that header is that SmartTree didn't display properly. Chad Killingsworth On Wednesday, December 11, 2013 6:00:18 AM UTC-6, RustyLogic wrote: Been there... In IIS: 1. go to /Sites/Default Web Site/CMS/WebClient 2. Open the HTTP ResponseHeaders 3. Delete the header:X-UA-Compatible: IE=EmulateIE7 4. You can now set it to whatever you like within your projects in the page headers (or do it globally but some of your older projects might still need IE7 to display properly in smartedit) Ta, John On Tuesday, December 10, 2013 10:56:36 PM UTC, 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/groups/opt_out.
Re: Render IE8 as IE8 in smartedit
Very true but works fine in 11.1 :) On Wednesday, December 11, 2013 3:05:45 PM UTC, Chad Killingsworth wrote: In version 10, the side effect of removing that header is that SmartTree didn't display properly. Chad Killingsworth On Wednesday, December 11, 2013 6:00:18 AM UTC-6, RustyLogic wrote: Been there... In IIS: 1. go to /Sites/Default Web Site/CMS/WebClient 2. Open the HTTP ResponseHeaders 3. Delete the header:X-UA-Compatible: IE=EmulateIE7 4. You can now set it to whatever you like within your projects in the page headers (or do it globally but some of your older projects might still need IE7 to display properly in smartedit) Ta, John On Tuesday, December 10, 2013 10:56:36 PM UTC, 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/groups/opt_out.
