W3C home > Mailing lists > Public > www-validator@w3.org > July 2011

Re: [VE][html5] http-equiv="X-UA-Compatible" should be valid

From: Jukka K. Korpela <jkorpela@cs.tut.fi>
Date: Sun, 31 Jul 2011 23:18:05 +0300
Message-ID: <4E35B87D.8070403@cs.tut.fi>
To: www-validator@w3.org, jfrench@ixley.com
31.07.2011 18:53, Leif Halvard Silli wrote:

> Jeff French, Sat, 21 May 2011 10:21:42 -0700:
>> I'm not sure why this error comes up. This http-equiv value has been
>> around for at least a few years and seems like it should be valid.
>>
>> Bad value X-UA-Compatible for attribute http-equiv on element meta.
>> <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
>
> It is not necessary that it is valid, because there is  a valid way of
> inserting it, see http://www.w3.org/Bugs/Public/show_bug.cgi?id=12072

That discussion seems to revolve around comments before <!doctype>, 
though it mentions the X-UA-Compatible issue too. And it's a rather 
complicated discussion. (And I can't find a "valid way of inserting it" 
there.)

Meta tags with http-equiv="X-UA-Compatible" are used for various 
purposes, such as making some versions of IE behave by the 
specifications in some issues or just reasonably. For example, some 
versions of IE treat an Ascii hyphen "-" as a character that allows line 
break before and after it, and the "before" part is just absurd. The tag
<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7">
seems to cure this, though with some cost.

So are you sure that for _all_ issues that can be handled with 
X-UA-Compatible, there is an equally or better supported other way?

But this isn't really about the validator, this is about the 
_specification_ of HTML5.

-- 
Yucca, http://www.cs.tut.fi/~jkorpela/
Received on Sunday, 31 July 2011 20:18:32 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 25 April 2012 12:14:48 GMT