|
|
Rank: Advanced Member
Groups: Member
Joined: 5/19/2010
Posts: 35
|
Hi,
On our web application, we need to force IE8 mode in order for certain CSS elements to display properly. By default IE has the "Display Intranet Sites in Compatibility Mode" set to on, causing various elements to not display as they should on the server.
We can override this setting by do so by setting a Custom HTTP Header "X-UA-Compatible: IE8" on IIS 6, which fixed up the CSS problems. However this generates a "Not Implemented" error from eo_web.ashx - Practically there was a grid which wasn't databinding which should have been.
But what's really strange is when the "Display Intranet Sites in Compatability Mode" setting is switched off, everything works as it should regardless of the IIS settings. While it wouldn't be a huge problem to enforce this setting with group policies, it's not entirely clear what effect it may have on other intranet websites - Being able to set this per website would be much more ideal.
Is there anything we can do which might fix this?
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,194
|
Hi, A quick search turns up this page: http://msdn.microsoft.com/library/cc817574.aspxIt doesn't mention how to set it on IIS or per site, but since it's a meta tag, theoretically you can set it on a per page basis. Also, if you can create a test project/page that duplicates the "not implemented" error we will be happy to take a look. Thanks!
|
|
Rank: Advanced Member
Groups: Member
Joined: 5/19/2010
Posts: 35
|
Unfortunately setting the meta tag on a per-page basis (Or in this case within the Master Page) doesn't override the "Display Intranet Sites in Compatibility Mode" setting - It has to be set within the IIS itself.
I can't really create a test project as this error only occurs when on an IIS server, when "X-UA-Compatible: IE=8" has been set. Without this setting everything seems to work as it should, but for page formatting to display correctly we'll need to keep this setting on: There doesn't seem to be any other way to override the compatabilty mode setting.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,194
|
Hi,
In that case you can create a test page/project with specific setup instruction such as "adding X-UA-Compatible: IE=8 to IIS". We can then follow those instructions in our test environment and see if we can see the same problem. Generally we only focus on our controls and will not troubleshoot or advice our customers on IIS configuration unless it has to be configured certain way for our product to function. On the control side, we will have to see the problem in our environment in order to look further.
Thanks!
|
|
Rank: Advanced Member
Groups: Member
Joined: 5/19/2010
Posts: 35
|
No worries, I've mailed off a test project. Hope that can help!
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,194
|
Hi,
We tested the sample project and it works fine (we did have to change "TestFirefoxGrid" to "TestGrid" in Default.aspx.cs to make it compile. However we are not able to see any script error. IE's compatible view button does disappear once we add the header. But there is no script error.
The next thing we can try is if you can put the page online, then we will try to access it here and see if we can see the same error. The bottom line is we have to see the problem before we can make any sense of it.
Thanks!
|
|
Rank: Advanced Member
Groups: Member
Joined: 5/19/2010
Posts: 35
|
Hmm, very strange - I might have a further look into this one myself and get back to you.
|
|
Rank: Advanced Member
Groups: Member
Joined: 5/19/2010
Posts: 35
|
Ok, I've discovered that the issue is related to http://www.essentialobjects.com/forum/postst3885_Internet-Explorer-8-Issues.aspxThe 'removeExpression' function seems to also be highlighted here as the problem: I'll try and get another test project out to you based on the project causing the problems, but it could be a bit tricky to extract it from the functionality of the rest of the project. If it helps at all, the pages which give the error all have EO Grids as well as callbackpanels used for dynamically loading different grids.
|
|