I see that there is a dataarea that controls the X-UA-Compatible setting for Atrium. Is the same functionality available for Rich Displays? If so, can it be set at the display file level?
I have a Rich Display Program that needs to run inside an iFrame inside of a vendors web page, but we are having problems because the vendor page is in compatibility mode while the Rich Display is in edge mode.
Thanks,
Sean
IE Compatibility Mode
-
SeanTyree
- Profound User
- Posts: 76
- Joined: Fri Jan 11, 2013 6:11 pm
- First Name: Sean
- Last Name: Tyree
- Company Name: US HealthWorks
- State / Province: California
- Zip / Postal Code: 91355
- Country: United States
- Contact:
-
David
- Profound Logic Staff Member
- Posts: 690
- Joined: Fri Jan 04, 2008 12:11 pm
- First Name: David
- Last Name: Russo
- Company Name: Profound Logic Software
- Contact:
Re: IE Compatibility Mode
The IE compatibility mode setting can normally be made using a <meta /> tag in the "start.html" page. However...
IE looks at the parent page's compatibility mode setting and will apply it to any pages loaded into frames, regardless of the setting made in the frame page. There is no way around it, that I know of. This is actually why we introduced the option for Atrium -- our users had no way to control the setting in their pages before, Atrium's setting would override. So this allows our users to control the main Atrium page's compatibility mode setting, and hence that for their own pages.
Unfortunately, the only possible solution that I'm aware is to get the vendor to change the setting used in the main page. I think what's happening is that your vendor's page is downgrading the IE mode used in your RDF page to something we don't support, likelyIE7 mode...
IE looks at the parent page's compatibility mode setting and will apply it to any pages loaded into frames, regardless of the setting made in the frame page. There is no way around it, that I know of. This is actually why we introduced the option for Atrium -- our users had no way to control the setting in their pages before, Atrium's setting would override. So this allows our users to control the main Atrium page's compatibility mode setting, and hence that for their own pages.
Unfortunately, the only possible solution that I'm aware is to get the vendor to change the setting used in the main page. I think what's happening is that your vendor's page is downgrading the IE mode used in your RDF page to something we don't support, likelyIE7 mode...
-
David
- Profound Logic Staff Member
- Posts: 690
- Joined: Fri Jan 04, 2008 12:11 pm
- First Name: David
- Last Name: Russo
- Company Name: Profound Logic Software
- Contact:
Re: IE Compatibility Mode
Can you let me know if the main (vendor) page gives the following tags, and if so can you copy/paste a copy of them for me to look at?
- <!DOCTYPE>
- <meta http-equiv="X-UA-Compatible" />
-
SeanTyree
- Profound User
- Posts: 76
- Joined: Fri Jan 11, 2013 6:11 pm
- First Name: Sean
- Last Name: Tyree
- Company Name: US HealthWorks
- State / Province: California
- Zip / Postal Code: 91355
- Country: United States
- Contact:
Re: IE Compatibility Mode
Hey David,
Strange stuff here. We have one program that when called inside their iFrame works perfectly, and another (with much less functionality) which displays a blank screen. If they run it in a seperate iFrame from the regular page they can repeat the problem by turning compatibility mode off/on.
I will send the DOCTYPE & http-equiv settings as soon as I get them.
Thanks,
Sean
Strange stuff here. We have one program that when called inside their iFrame works perfectly, and another (with much less functionality) which displays a blank screen. If they run it in a seperate iFrame from the regular page they can repeat the problem by turning compatibility mode off/on.
I will send the DOCTYPE & http-equiv settings as soon as I get them.
Thanks,
Sean
-
SeanTyree
- Profound User
- Posts: 76
- Joined: Fri Jan 11, 2013 6:11 pm
- First Name: Sean
- Last Name: Tyree
- Company Name: US HealthWorks
- State / Province: California
- Zip / Postal Code: 91355
- Country: United States
- Contact:
Re: IE Compatibility Mode
Hi David,
I sent you the tag settings in an email.
Sean
I sent you the tag settings in an email.
Sean
-
David
- Profound Logic Staff Member
- Posts: 690
- Joined: Fri Jan 04, 2008 12:11 pm
- First Name: David
- Last Name: Russo
- Company Name: Profound Logic Software
- Contact:
Re: IE Compatibility Mode
See my reply to your email for specifics on your case, but for general purpose and the benefit of other forum users:
A meta tags (use only one) can be used in the page to request the desired IE rendering mode. If one of these are given, it will override the user's Compatibility View settings in IE and you'll be guaranteed to get the requested mode:
Request latest avail. IE rendering mode:
Request specific IE rendering mode (or latest avail):
Also the page should have a valid DOCTYPE tag to ensure Standards Mode, we recommend using an HTML5 DOCTYPE, like this:
This will guarantee the requested (or latest avail) IE Standards Mode. Profound UI / Genie require IE8 Standards at minimum.
What you are saying about some screens working and others not working in Compatibility View makes perfect sense. Compatibility View uses IE7 Standards Mode. We do not develop/test/support anything less than 8, so there are going to be issues when running in Comatability View, it's simply not supported. Some screens may work 'by chance', and others will fail where our rendering process uses some coding techniques which do not work in IE7.
Unfortunately, Internet Explorer will apply the parent page's rendering mode to ANY/ALL pages running in frames, regardless of the mode requested by the pages in the frames. There is no way around this that I'm aware, so the only solution I know would be for the vendor to make adjustments in their page.
A meta tags (use only one) can be used in the page to request the desired IE rendering mode. If one of these are given, it will override the user's Compatibility View settings in IE and you'll be guaranteed to get the requested mode:
Request latest avail. IE rendering mode:
Code: Select all
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
Code: Select all
<meta http-equiv="X-UA-Compatible" content="IE=10" />
Code: Select all
<!DOCTYPE html>
What you are saying about some screens working and others not working in Compatibility View makes perfect sense. Compatibility View uses IE7 Standards Mode. We do not develop/test/support anything less than 8, so there are going to be issues when running in Comatability View, it's simply not supported. Some screens may work 'by chance', and others will fail where our rendering process uses some coding techniques which do not work in IE7.
Unfortunately, Internet Explorer will apply the parent page's rendering mode to ANY/ALL pages running in frames, regardless of the mode requested by the pages in the frames. There is no way around this that I'm aware, so the only solution I know would be for the vendor to make adjustments in their page.
Who is online
Users browsing this forum: No registered users and 3 guests