why is my page opened by ie8 with ie7 interpreter as standard? - internet-explorer-8

Hi i have made a website. And cause of some crazy reason i don't figure out the ie8 runs it with Browsermode: i8 and Documentmode: ie7 (standard). Why he doesn't use ie8 for both?

Did you put a valid DOCTYPE into your pages? Otherwise IE8 will run in compatibility mode.
See this blog post for details.

Related

IE8 Browser Mode vs IE8 in XP Mode CSS renders differenty?

Please forgive me if I placed this in the wrong section of Stack Exchange, I will be happy to repost elsewhere, Im just not sure which section to go to.
Why does IE8 display differently in Browser Mode (which is accessible through the IE10 F12 Developer Tools) than in XP Mode?
It seems that the CSS is rendered differently. Does anyone know the details as to why this occurs?
IE8 Browser Mode vs IE8 in XP Mode CSS renders differenty?
Yep, that's a pretty well-documented problem. It may be called compatibility mode, but the fact is, it isn't really all that compatible.
This is why it's generally considered a bad idea to use compatibility mode to do your testing.
Ultimately the only reliable way to test that a site works in IE8 is to actually load it in a real copy of IE8. XP Mode is a good way to do that.
I agree it's more of a hassle than switching the mode in IE10, but unfortunately, that's the way it is.

ie8 -> ie9 upgrade and x-ua

I have a corporate app with ie8 as the current forced browser. Machines are locked down tight and i can't even test on anything else because I can't install anything else. There are no other version of ie in use. it is 100% ie8. no 7, no 9. And they default to run in ie 7 compat / ie8 quirks mode.
In order to get stuff working right and to force standards mode, i had to use the html 5 DTD (to future-ready the site for mobile dev coming down the pipe instead of xhtml4) and
<meta http-equiv="X-UA-Compatible" content="IE=8">
heading in the template.
I have no information when they might go to ie9... or even skip to ie10.
Whats the best way to future proof this intranet site without being able to test it in ie9 or ie10, or a gecko browser?
I tried to follow tight standards and keep it clean with jquery and css and no in-line markup.
What does an ie9 do when it sees the ie=8 x-ua header? Should i use something else instead of this? I may not be working this app when the move comes. What notes should I leave for a future developer to be aware of?
Leave the X-UA-Compatible set to IE=8. IE9 and IE10 will try to switch to IE8 mode.

Can I depend on IE's Browser mode and doctype to debug issues for IE 8 and below + Quirks?

If I use the F12 Developer Tools to debug for IE, can I depend on the "Browser Mode" and "Doctype" to debug issues for IE8 and below?
By debugging I mostly mean for overall page behavior... HTML/CSS, A client says "The dropdown doesn't work in IE8", I have IE9... Instinct is to hit F12 and change the doctype or browser mode and test.
Short answer, no.
I would not recommend using compatibility mode. I have never quite understood why MS doesn't seem to do what Mozilla and Google do which is, disallow the use of deprecated tags. As an example, at my work, we have two tiers of browser usage, tier 1 and tier 2. Tier one consists of: Safari (oddly enough, we get quite a few customers buying via their iPads), Chrome, Firefox and IE9. Tier two is: IE8 and the rest of the pile. Recently, we had a bug where some checkboxes where not rendering correctly in **only IE8**; but worked fine in IE7 and IE9. The moral here is that using compatibility mode is testing under an assumption, and if you want thorough and correct testing, you cannot assume anything.
You can try to use the Quirks mode, but that's not 100% the same. If you are lucky, you will hit the same bug also in quirks mode.
The only sure way is to use a IE8. There are cross-browser testing tools that enable you to do so without any installs.
Just for bug reporduction purposes http://www.modern.ie/virtualization-tools offers some VM-s you can use.

MHTML on HTTPS with IE7

When using MHTML over https in IE7, IE7 shows the non-secure items popup.
I believe this is due to the mhtml: prefix. IS this actually a bug? or is there a workaround for it?
Starting here is a good thread kind of explaining some options. We just ended up not supporting IE7 since it's only a couple percent of our users now anyway.
http://www.phpied.com/mhtml-when-you-need-data-uris-in-ie7-and-under/#comment-72154

Strange HTTP_USER_AGENT for IE8 in PHP

How is that possible?
http://img191.imageshack.us/img191/7080/wtfsg.jpg
Any solution to separate IE8 from IE7?
To quote this article on IEBlog:
IE8 will send the “MSIE 7.0” version information when viewing sites with Compatibility View enabled. (...) A new “Trident” token in the User-Agent string allows your code to detect Internet Explorer 8 clients even when they are using the Compatibility View feature.
To wit, your page is displayed in Compatibility mode, hence the UA change.
In this case you need to check from your developer toolbar if you are rendering your site as IE7.
You can get to the developers toobar by hiting F12 and checking the browser mode and puting it to IE 8.

Resources