I have a map with points on it which the user hovers over to reveal further information.
The problem I have is hard to explain because it only seems to be a problem when the user views the page in IE and when it is hosted on my server. Exactly the same code on the jsfiddle page below works fine.
http://jsfiddle.net/FbYEW/
What happens when hosted on my server is the z-indexes on the popups do not work and the popups appear underneath the other spots. Can anyone think why this might be... it's very frustrating not to be able to replicate the problem for anyone to see.
EDIT:
I was viewing the page hosted on my server in compatibility mode on IE8. If you look at the jsfiddle page in IE the same problem occurs - so nothing to do with my server after all... oops
When hosted from your server, the page is rendering in a browser mode other than IE9 Standards Mode.
For example, if it's rendering in IE7 Mode or Quirks Mode, z-index problems are expected.
Hit F12 to bring up the Developer Tools, and see which it is.
There are many different possibilities as to why this is happening, see:
http://hsivonen.iki.fi/doctype/#ie8modes
If you just want to fix it without working out where the problem is coming from:
<meta http-equiv="X-UA-Compatible" content="IE=edge">
Related
We're experiencing an issue with our site, YouSIMUL8.com. We use this site to allow people to run simulations on the web. An example simulation can be found at http://www.yousimul8.com/watch.php?x=4d5005d769d31.
If you have a look at what's going with this page, when you press play it loads an iframe in and the simulation is shown there.
I've been speaking to a customer who has been having difficulty using the site. When they open a simulation, only the border of the iframe is shown and nothing else happens. This is using IE10. The problem disappears when compatibility view is turned on.
I cannot replicate this issue with IE10 no matter how hard I try. The customer's IT is outsourced so they cannot access the settings, developer tools or console in IE.
So the question is this: What configuration of the client's machines could cause this behavior?
To force to the rendering of the page to latest version of IE, overriding the automatic compatibility view, try to use the Meta Tag Compatibility View:
<meta http-equiv="X-UA-Compatible" content="IE=edge">
Have a look to this StackOverflow post.
I am completely puzzled and discouraged. There is the following problem on a website: Google AdSense banners are not showing up in Internet Explorer until the browser is somehow interacted with.
I have checked it on four completely different computers and the problem looks the same: the ads are not showing at all, until you do one of the following:
resize the window, or
press "alt" button on the keyboard, or
open up the console (F12)
In other words, the ads show up right in their right place after I somehow interact with the browser window. And that is happening in Internet Explorer 11! On four totally different computers.
I can't wrap my mind about it. Does anybody have any kind of idea what this might be?
I've finally found the solution. It was indeed a "ie-compatibility" issue, yet not obvious and not that easy to find.
Probably some wordpress plugin added the following line to the header:
<meta http-equiv="X-UA-Compatible" content="IE=7"/>
I changed it to
<meta http-equiv="X-UA-Compatible" content="IE=8"/>
And it worked. Why do I say it was not easy to find? Well, I played a lot with compatibility settings in the IE browser and nothing worked. And again the way the bug represented itself would never make me think that such line was responsible.
I'm developing a website that displays fine in FF or Chrome, but when running on IE, it displays the message below and turn view into compatibility, thus the layout fails to display correctly and some tags and controls such asp menu disappear (still exist in html code).
Can anyone help me solve this problem?
Error Message: A problem displaying localhost caused internet explorer to refresh the page using compatibility view!
There are most likely markup validation errors in your page that is causing IE to fall back to compatibility mode that FF or Chrome may ignore. Ensure that your page passes validation.
Try going here W3C Markup Validation Service and running your HTML or URL through to look for any blatant errors.
The other possibility is that you are explicitly setting the meta tag for IE to force compatibility, e.g.
<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" />
If so, remove it.
The site I am working on uses Facebook Javascript SDK, as described here https://developers.facebook.com/docs/reference/javascript/, to allow users to login. The site is an ASP.NET MVC site.
It works on latest versions of Chrome, Firefox, Safari and also IE9.
However in windows 8 consumer preview using IE10 (in normal and compatibility mode) when logging into Facebook the popup window goes white and doesn't close. If close manually and refresh the original page I see that I am logged in.
I have looked through all other SO questions and searched the web. I have tried all the solutions and none of them work.
I am using the channelUrl correctly and it works in the other browsers. I also tried the IE10 bug fix here http://www.hanselman.com/blog/BugAndFixASPNETFailsToDetectIE10CausingDoPostBackIsUndefinedJavaScriptErrorOrMaintainFF5ScrollbarPosition.aspx
There really isn't much different from my code and the Facebook examples. So I think there is either a problem with IE10 or the Facebook API when using IE10.
Has anyone had similar problems and found a solution?
The problem was in the HTML. The meta tag for http-equiv was set to
<meta http-equiv="X-UA-Compatible" value="IE=8">
This causes IE10 to display the web page in IE8 mode. Changed this to 9 as it was meant to be and the Facebook popup box disapears.
I am completely confused - I have a website that renders perfectly in IE8 when run through Cassini (in Visual Studio) but has several messed up elements (style/look) when deployed to localhost and viewed through the same browser (IE8).
I have run Beyond Compare 3 on the html and CSS files and they are exactly the same. Are there any circumstances where IIS7 could be somehow sending extra/different information to the browser? Has anyone run across something like this before?
Note that Chrome and Firefox both render the same webpage just fine through Cassini and IIS7.
(Update)
What Browser Mode and Document Mode does IE8 Developer Tools think you are in if you press F12?
When running from Cassini (http://localhost:22120), IE8 stays in IE8 mode (with the option for turning on IE7 compatibility view) and everything looks great.
When running from IIS7 (http://{machine name}), IE8 automatically goes into in IE8 Compat View, IE7 standards and things look horrible.
My assumption (as mentioned in my comment earlier) was that IE is working in a different rendering mode, depending on whether you are using IIS or Cassini, and this is causing the layout differences. It actually appears to be IE that is causing this, based on the settings found in Tools | Compatibility View Settings. There are two check boxes:
Display intranet sites in Compatibility View - this is checked by default.
Display all websites in Compatibility View - this is not.
Either way, you should use the standard meta tag to force the mode you wish to be rendered in.
<meta http-equiv="X-UA-Compatible" content="IE=8" />
Hope this helps.
I think the best solution I have found is not far from Paul's one but it tells the browser to use your Internet Explorer version which solved other problems I have with content="IE=8".
Here it is:
<meta http-equiv="X-UA-Compatible" content="IE=Edge" />
Actually I had the same issue. IE8 has a compatability settings dialog under tools menu. There is a check box which indicates "Display intranet sites in compatability mode".
And not that IE7 compatability mode is not the same as using ie7, there are some differences.
One side note to this issue:
if the same page renders differently on different servers but in the same IE8 browser, check your url - IE8 automatically displays in compatibility mode if the domain is not fully qualified.
If the page content is the same then compare the headers that the servers are sending with the page.
After kicking this around a bit I though about compatibility mode. Try manually forcing IE8 to render the page in compatibility mod. If the render doesn't change then you know that the issue is because IE is rendering that page in compatibility mode when reading it from that web server.
If the latter is the case look into http://msdn.microsoft.com/en-us/library/dd567845%28VS.85%29.aspx