This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 8608 - W3C Validator errors reported on HTML5 spec
Summary: W3C Validator errors reported on HTML5 spec
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://validator.w3.org
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-04 00:13 UTC by Don Brutzman
Modified: 2010-10-04 13:55 UTC (History)
6 users (show)

See Also:


Attachments

Description Don Brutzman 2010-01-04 00:13:10 UTC
http://validator.w3.org/check?uri=http%3A%2F%2Fdev.w3.org%2Fhtml5%2Fspec%2FOverview.html&charset=%28detect+automatically%29&doctype=Inline&group=0

Line 218, Column 735: required attribute "TYPE" not specified

Line 25722, Column 8: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag

Line 25723, Column 8: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag

Line 27375, Column 10: document type does not allow element "TFOOT" here; assuming missing "TABLE" start-tag

Line 27379, Column 10: end tag for "TABLE" which is not finished

Line 72252, Column 4: end tag for "TABLE" omitted, but its declaration does not permit this
Comment 1 Henri Sivonen 2010-01-04 08:00:05 UTC
The most reasonable fix would be to use HTML5 itself (and to make pubrules allow specs HTML5 to use HTML5).
Comment 2 Ian 'Hixie' Hickson 2010-01-11 11:18:04 UTC
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Accepted
Change Description: see diff given below
Rationale: I've fixed the problems I could find (partially by just removing some of the examples, since they are showing HTML5 features and thus aren't HTML4-compliant).
Comment 3 contributor 2010-01-11 11:20:01 UTC
Checked in as WHATWG revision r4574.
Check-in comment: Remove some examples that use HTML5 features from the W3C copy of the spec, since W3C wants the HTML5 spec to use HTML4.
http://html5.org/tools/web-apps-tracker?from=4573&to=4574
Comment 4 Don Brutzman 2010-01-26 08:20:18 UTC
http://validator.w3.org/check?uri=http%3A%2F%2Fdev.w3.org%2Fhtml5%2Fspec%2FOverview.html&charset=%28detect+automatically%29&doctype=Inline&group=0

still reports one warning (which wasn't reported before):
================================================
No Character encoding declared at document level

No character encoding information was found within the document, either in an HTML meta element or an XML declaration. It is often recommended to declare the character encoding in the document itself, especially if there is a chance that the document will be read from or saved to disk, CD, etc.
================================================

p.s. the validator service was quite speedy on this very large document, pretty impressive.
Comment 5 Ian 'Hixie' Hickson 2010-02-14 02:56:38 UTC
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: no spec change
Rationale: The remaining error message is a bug in the validator. The spec says that a document that consists of pure ASCII (as the spec does) doesn't need a character encoding declaration.