W3C home > Mailing lists > Public > www-validator@w3.org > January 2010

Re: W3C Validator trips on Google Frame meta line with HTML5 doctype

From: Gordon <gordeon@gmail.com>
Date: Thu, 28 Jan 2010 01:19:07 -0800
Message-ID: <a4235b1b1001280119r675afa18h89a0d6c9807d84b6@mail.gmail.com>
To: "Michael A. Peters" <mpeters@mac.com>
Cc: www-validator@w3.org
Maybe I'll just let this one Chrome Frame line fail the validation,
knowing that the rest does validate anyway. I don't think it's worth
the UA sniffing just for the sake of this line. I take it the W3C
validator will never accept this line as valid?


On Wed, Jan 27, 2010 at 9:29 PM, Michael A. Peters <mpeters@mac.com> wrote:
> Michael A. Peters wrote:
>>
>> Gordon wrote:
>>>
>>> When validating the HTML5 doctype, the W3C Validator seems to trip
>>> over on the Google Frame meta tag.
>>>
>>> <meta http-equiv="X-UA-Compatible" content="chrome=1">
>>>
>>>
>>> http://code.google.com/chrome/chromeframe/developers_guide.html#Making_Your_Pages_Work
>>>
>>> Any thoughts?
>>>
>>>
>>
>> Would sending it as a header instead of in meta tag trigger Google Frame?
>> Just curious, for dynamic content it may be a solution.
>>
>
> Even better (if dynamic content), sniff the UA and only add the meta tag if
> it contains the string chromeframe.
>
> It would still fail validation when using a link to validator from page and
> the browser is IE with chromeframe (because the validator sends the same
> accept string) but it would pass validation for all other browsers or when
> specifying the url, and the header is only needed when the user is using IE
> with chromeframe anyway.
>
Received on Thursday, 28 January 2010 09:19:41 GMT

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