1

I have been researching all over the internet about this, and unfortunately cannot find out why this is happening. It seems to only be happening in internet explorer 9, on certain computers.

The entire page looks like a mess only in IE 9 (some computers):

enter image description here

The URL of the website is Here

Can anyone tell me why this is happening in IE9?

(NOTE: Compatibility view cleans it, but then the Js/jQuery doesn't work right).

Kijewski
  • 25,517
  • 12
  • 101
  • 143
Marcus Bennett
  • 31
  • 4
  • 1
    Hi Marcus, could you share the relevant part of your code (css and html structure of the buggy part)? Also, I did a quick check in the site's source code, and my html validator gives me **hundreds** of just html errors. Of which I saw one that you put an `` tag inside another `` tag. With all these scripting errors, it's hard to say what is at fault here. – paddotk Jun 19 '12 at 22:59
  • Hello poepje, you found double html tags on the homepage? I wasn't able to locate another `html` tag in this script. – Marcus Bennett Jun 19 '12 at 23:06
  • You have [2386 HTML Validation Errors](http://validator.w3.org/check?uri=http%3A%2F%2Fwww.go-optic.com%2F&charset=%28detect+automatically%29&doctype=Inline&group=0)! It's no wonder you have problems with IE. – Sparky Jun 19 '12 at 23:10
  • I checked again and see it now, the error is that you have code that's inside the but not the nor tag. Also, the html validator says ' previously mentioned'. – paddotk Jun 19 '12 at 23:14
  • As for the last one, I'd suggest to do it like this instead: ` ` – paddotk Jun 19 '12 at 23:16
  • Thank you for your comment poepje, but can you explain what you mean here? Maybe in an answer below? – Marcus Bennett Jun 19 '12 at 23:19

3 Answers3

1

For some reason, IE thought that the site was in my intranet, and rendered it in Compatibility Mode (there's a setting in IE to automatically render intranet sites in CM). When I unchecked the box to "automatically detect intranet network", the site rendered correctly.
So your real question is how does IE determine the intranet network, and how can you force your page to NOT render in Compatibility Mode... something like this.

Community
  • 1
  • 1
Scott M
  • 91
  • 5
0

Going on a whim here, but I think it's the usage of inline-block. I don't have IE9 installed to a point where I can use it's developer console to further inspect, but IE is known to be very bad about displaying inline-block elements.

In Google Chrome's console, I am able to replicate the same appearance using float:left as opposed to display:inline-block, so that should solve that piece of the issue.

Edit: The only syntax issue I see with the HTML is the placement of the </head> tag, which is not adjacent to the <body> tag.

Edit 2: As far as the outlining issue goes, try using this answer to another question.

Edited yet again to fix the display of the tags.

Community
  • 1
  • 1
Nicholas Anderson
  • 404
  • 2
  • 7
  • Not all though ie9 browsers, only some. – Marcus Bennett Jun 19 '12 at 23:00
  • Thank you for your input, but how about the blue borders? – Marcus Bennett Jun 19 '12 at 23:02
  • I thought those where highlights from an inspection program. I'll look into potential causes. As far as solutions to the problem, I would just use floats. Wherever you use `display:inline-block`, replace it with `float:left`. – Nicholas Anderson Jun 19 '12 at 23:05
  • Nicholas, I commend you for trying but until the OP fixes most of his [2300+ Validation Issues](http://validator.w3.org/check?uri=http%3A%2F%2Fwww.go-optic.com%2F&charset=%28detect+automatically%29&doctype=Inline&group=0), you're simply chasing something you'll never get your arms around. – Sparky Jun 19 '12 at 23:30
  • @Sparky672 Have you looked through the errors? The markup is getting dinged almost entirely for unescaped URLs, and meta attributes that won't affect the display of the page. The misplacement of the `` tag is a true markup error, but browsers will still load the stylesheets and scripts anyways. His syntax, although it should be fixed, will have no affect on the page's display. – Nicholas Anderson Jun 19 '12 at 23:34
  • Nicholas, How could anyone here have gone through all 2386 errors to verify that none of them could cause rendering issues? Invalid HTML is one of the leading reasons IE slips into Compatibility Mode. My point is that you should have a solid (valid and compliant) foundation before launching into fixes and workarounds. – Sparky Jun 19 '12 at 23:38
  • Thank you Nicholas for your answers and comments. It appears it was a compatibility issue with IE, which appears to be resolved. As for the validation issues, I will look into those. Thanks again. – Marcus Bennett Jun 19 '12 at 23:43
  • Actually, I read your comment about the misplaced `` tag, can you explain why it is misplaced? Thank you. – Marcus Bennett Jun 19 '12 at 23:47
  • @Marcus Bennett You have `` elements sifted throughout the document, these should be all located within the ``. Also, the ` – Nicholas Anderson Jun 20 '12 at 00:00
  • You were very helpful Nicholas, thank you for your efforts. Unfortunately another answerer was able to provide the exact cause of the issue, which is the compatibility issue being triggered. However, I do thank you again for all of your help and will look into resolving these other issues. – Marcus Bennett Jun 20 '12 at 00:13
0

I noticed that you have blank space above your doctype. IE hates this. The doctype needs to be the very first thing in the file.

You also have over 2300 HTML validation errors that should be investigated and rectified. Again, IE is very sensitive to invalid HTML.

Sparky
  • 98,165
  • 25
  • 199
  • 285
  • Thank you Sparky, top space removed, but still the same issue. ;( – Marcus Bennett Jun 19 '12 at 23:25
  • @MarcusBennett, then look at my second point. That's horrifically invalid HTML... IE is notorious for not dealing with this as well as others. – Sparky Jun 19 '12 at 23:27
  • @Bergi, what does have to do with my answer? – Sparky Jun 19 '12 at 23:54
  • It was @MarcusBennett. The validator auto-detected Doctype "XHTML 1.0 Transitional", which it is not. Served as normal HTML, there should be fewer errors – Bergi Jun 20 '12 at 07:38