Re: X-UA-Compatible causes extraneous errors in the validator for an html5 page

On 6 Apr 2012, at 23:44, Robert K. Foster wrote:
>  Line 8, Column 52: Bad value X-UA-Compatible for attribute http-equiv on element meta.
> <meta http-equiv="X-UA-Compatible" content="IE=9" />

That is invalid HTML 5.

From the spec: Conformance checkers must use the information given on the WHATWG Wiki PragmaExtensions page to establish if a value is allowed or not: values defined in this specification or listed on the aforementioned page must be accepted, whereas values not listed in either this specification or on the aforementioned page must be rejected as invalid. Conformance checkers may cache this information (e.g. for performance reasons or to avoid the use of unreliable network connectivity).

 — http://www.w3.org/TR/html5/the-meta-element.html#the-meta-element

Frankly, having a W3C spec depend on a freely editable third party resource seems crazy to me. Hopefully it will be improved before HTML 5 becomes a recommendation. 

>  Line 45, Column 7: Stray end tag head.
>  Line 47, Column 6: An body start tag seen but an element of the same type was already open.

You terminated the head (the end tag is optional) and started the body (the start tag is optional) by on line 33 by including a <div> (since div elements cannot appear in the head but can appear in the body).

-- 
David Dorward
http://dorward.me.uk