- From: Michael A. Peters <mpeters@mac.com>
- Date: Wed, 27 Jan 2010 21:29:35 -0800
- To: Gordon <gordeon@gmail.com>
- Cc: www-validator@w3.org
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 05:30:11 UTC