Bug 6747 - Direct input of HTML5 seems to validate anything
: Direct input of HTML5 seems to validate anything
Status: RESOLVED FIXED
Product: Validator
HTML5
: HEAD
: PC Linux
: P2 minor (vote)
: 0.8.6
Assigned To: Ville Skytt
: qa-dev tracking
:
:
:
:
:
  Show dependency treegraph
 
Reported: 2009-03-30 02:59 UTC by Eric Anderson
Modified: 2010-03-02 19:55 UTC (History)
1 user (show)

See Also:


Attachments
HTML5 doc that should not validate (196 bytes, text/html)
2009-03-30 02:59 UTC, Eric Anderson
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Eric Anderson 2009-03-30 02:59:47 UTC
Created attachment 674 [details]
HTML5 doc that should not validate

When doing direct input of a HTML5 document the validator seems to return it
being ok no matter what. Attached is a small test file that shows the problem.
The <body> tags is purposely mistyped as <bodly>. If I upload this file then I
get an error as expected. But if I copy and paste the text in the direct input
then it says the document is ok even though it is not.

After a bit of testing I discovered that if I explicitly tell it that the
content is HTML5 then it detects the problems fine. So it only seems to be a
problem if the doctype is automatically detecting the doctype (even though it
is automatically detecting HTML5 correctly).
Comment 1 Ville Skytt 2009-09-15 19:11:34 UTC
That's right; when not overriding doctype or charset, validator ended up
passing a malformed Content-Type header to the HTML5 validator.  This should be
fixed in http://www.w3.org/mid/E1MndLh-0001IU-EA%40lionel-hutz.w3.org , but it
remains to be examined why this resulted in marking everything as valid
(probably the HTML5 validator output was something the markup validator
couldn't understand).
Comment 2 Ville Skytt 2009-09-15 19:26:49 UTC
(In reply to comment #1)
> it remains to be examined why this resulted in marking everything as valid
> (probably the HTML5 validator output was something the markup validator
> couldn't understand).

Indeed.  This should be fixed in
http://www.w3.org/mid/E1Mnddq-0001uN-Gh%40lionel-hutz.w3.org
Comment 3 Ville Skytt 2010-03-02 19:55:15 UTC
Fix is included in 0.8.6.