Setting the X-UA-Compatible response header has some aspects I find remarkable.
<meta http-equiv="X-UA-Compatible" content="IE=6"> or <meta http-equiv="X-UA-Compatible" content="IE=5"> ... - content="IE=5" or content="IE=6" throws IE8b1 in quirksmode, even if the document has a standards Doctype. while - content="IE=8" or content="IE=9" ... throws IE8 in Standards-IE8-Mode, even if there is /no/ doctype (or a quirksmode triggering doctype). and - content="IE=7" throws IE8 in Standards-IE7-Mode, even if there is /no/ doctype (or a quirksmode triggering doctype). Other content like "IE=4" or "IE=nonsense" keeps IE8 in Standards-IE8-Mode if there is a standards doctype, so I think they are simply ignored. But "IE=5" or "IE=6" are not ignored, they have a meaning that is not documented yet afaik. So the meta-switch is able to take precedence over the doctype switch in any case. Ingo -- http://www.satzansatz.de/css.html http://www.dolphinsback.com ______________________________________________________________________ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
