HTML5 Parse Errors in Tokenization Stage

@@ -48,17 +176,16 @@ The & character must introduce a reference. -

An & (U+0026 - AMPERSAND) character which +

An & character which is not part of any reference appears in the input stream. - The document is non-conforming.

+ The document is non‐conforming.

Any & character in URI (or IRI) - must be escaped as &.

Any & character in URI (or IRI) + must be escaped as &.

The & character must be the first character of a reference: -

Named entity reference

&entity-name;

where entity-name is the name of the @@ -134,7 +261,7 @@

The string &# must be the first two characters of a reference: -

Numeric character reference

&#d;

where d is the decimal representation of @@ -189,20 +316,22 @@

Comments: In HTML documents, comments must be introduced by - . Strings <! not followed + -->. + Strings <! not followed by -- and <!- not followed by - are not valid open delimiters for comments.
Marked sections, including CDATA sections: Marked sections are not allowed in HTML documents.; Marked sections are not allowed in HTML document.
Markup declarations: Markup declarations, except DOCTYPE - and comment declarations, are not allowed in HTML documents.; Markup declarations, except for DOCTYPE + and comment declarations, are not allowed in HTML document.
String <!: String <! must be escaped as - <!.

@@ -273,11 +402,12 @@ embed, param, area, col, and input elements.

<script/>

The polytheistic slash cannot be used for script element. Even for an empty script element, - there must be an explicit end tag </script>.

+ there must be an explicit end tag + </script>.

NOTE: Though some user agents interpret polytheistic slash for script element as the @@ -289,12 +419,15 @@

These elements are themselves non-conforming.

<command/>, <event-source/>, - <source/>

<nest/><source/>Future revision of HTML5 parsing algorithm is expected to allow polytheistic slash for these elements.

<a/>, <p/>

These elements are not always empty and therefore - polytheistic slash is not allowed.

<p></p>

Note that, unlike in XML, the polytheistic slash has @@ -314,16 +447,31 @@ (<?xml-stylesheet ...?>), are not allowed in the HTML syntax. The document is non-conforming.

<?xbl?> (XBL Association)

An XBL binding cannot be associated by + PI in HTML + document. Use binding property in CSS + style sheet as: +

<style>
+p {
+  binding: url(binding.xbl);
+}
+</style>

<?xml?> (XML declaration)

XML declaration is unnecessary for HTML documents.

<?xml-stylesheet?> (XML style sheet - PI

PIUse HTML link element with rel attribute set to stylesheet (or, alternate stylesheet for an alternate style - sheet).

<?php?> (PHP code)

<link rel=stylesheet href="path/to/stylesheet.css">

<?php?> or + <? ... PHP code ... ?> + (PHP code)

The conformance checker does not support checking for PHP source documents.

Other processing instructions

Only white space characters and comments are allowed - before the DOCTYPE.

DOCTYPEnot

Only body, dd, dt, - head, html, li, +

Only body, colgroup, dd, + dt, head, html, li, ol, option, optgroup, - p, rb, rp, rt, or - ul end tag can be implied in HTML documents. + p, rb, rp, rt, + tbody, td, tfoot, + th, thead, tr, + ul end tag can be omitted in HTML documents. For any element except for void element, there must be an explicit end tag.

HTML canvas element: Though the element is void in earlier versions of Safari, + the canvas element is no longer + defined as empty. There must be an end tag + </canvas>.

Note that misnesting tags, such as <a><b></a></b>, are not allowed and they also cause this error.

The document contains a DOCTYPE declaration that is different from HTML5 DOCTYPE (i.e. - <!DOCTYPE HTML>). The document is non-conforming.

+ <!DOCTYPE HTML>). + The document is non‐conforming.

The document might or might not be conformant to some version of HTML. However, conformance to any HTML @@ -542,6 +702,19 @@

For any end tag in HTML document, there must be a corresponding start tag.

+ +

HTML base, basefont, + bgsound, br, col, + embed, frame, hr, + image, img, input, + isindex, link, meta, + param, spacer, or wbr element: End tag is not allowed for these elements, since + those content must always be empty. Remove end tag.

$0

For example: -

The head element must contain exactly one - title child element.
The tr - element must contain one or more td or th - child element.

HTML head element: There must be a title child element.
HTML html element: There must be a head child element followed + by a body element.
HTML tr element: There must be + one or more td or th child element.

p

For example, an HTML document fragment - <div><p>Hello!</p> World!</div> + <div><p>Hello!</p> World!</div> is non-conforming, since a word World! does not belong to any paragraph. (If not part of any paragraph, what is it!?) A conforming example would be: -

<div><p>Hello!</p> <p>World!</p></div>

<div><p>Hello!</p> <p>World!</p></div>

If the parent element does not allow block-level elements as content

If the element with the error is the html element - that is the root element of an XHTML document

headultableselect

In an XHTML document, the root html - element must have an xmlns attribute - whose value is set to - http://www.w3.org/1999/xhtml.

If the element with the error is blink, center, or marquee element

These elements are not part of the HTML standard. Use CSS for styling control.

button, datalist, form, +

button, datalist, + fieldset, form, input, label, optgroup, option, output, rb, rp, rt, ruby, @@ -682,6 +851,36 @@ + + This element is not allowed as a root + element. + +
An element that is not allowed as the root element + is used as the root element of the document. The document is + non-conforming, as far as the conformance checker can tell.
+ +
+
html element in an XHTML document
+
In XHTML document, the root html + element must have an xmlns attribute as: +
<html xmlns="http://www.w3.org/1999/xhtml">
+
rss element
+
The document is written in some version of RSS.
+
The conformance checker does not support any version + of RSS. Use Atom 1.0 for feed documents.
+
feed element
+
The Atom feed element must be + in the http://www.w3.org/2005/Atom + namespace as: +
<feed xmlns="http://www.w3.org/2005/Atom">
+
+
The conformance checker does not support Atom 0.3. + Use Atom 1.0 for feed documents.
+
+ + + There is no $0 @@ -818,6 +1017,87 @@

Attribute Value Errors
+ + Character encoding name $0 + is not registered. + +
The specified character encoding name is not registered to + IANA. Use of registered character encoding name + is a good practice to facilitate interoperability.
+ +
+
EUC-TW
+
EUC-TW is not registered. Unfortunately, there + is no registered name for that character encoding. Use + Big5 encoding with character encoding name Big5 + if it is enough to represent the document.
+
ISO-2022-JP-1
+
ISO-2022-JP-1 is not registered, nevertheless + this character encoding name is documented in + RFC 2237. Use + ISO-2022-JP-2 instead, since that character encoding + is a superset of ISO-2022-JP-1.
+
ISO-2022-JP-3, ISO-2022-JP-3-plane1
+
These names are not registered and obsoleted in favor of + ISO-2022-JP-2004 and + ISO-2022-JP-2004-plane1.
+
ISO-2022-JP-2003, + ISO-2022-JP-2003-plane1
+
These names are not registered and corrected to + ISO-2022-JP-2004 and + ISO-2022-JP-2004-plane1.
+
ISO-2022-JP-2004, + ISO-2022-JP-2004-plane1
+
These names are not registered. Unfortunately, there is + no registered name for these character encodings.
+
UTF-8N
+
UTF-8N is not registered. Character encoding + name UTF-8 represents UTF-8 encoding with or + without BOM.
+
+ +
WARNING: This error might be raised for + a registered character encoding name, since the character encoding + name database of the conformance checker is not complete yet.
+ + + + + $0 is a private + character encoding name. + +
The specified character encoding name is a private name and + not registered to IANA. Use of registered character + encoding name is a good practice to facilitate interoperability.
+ +
+
x-euc-jp
+
Use EUC-JP for the Japanese EUC + character encoding.
+
x-sjis
+
Use Shift_JIS for standard Shift encoding scheme of + JIS coded character set, or Windows-31J + for Microsoft standard character set as implemented by + Microsoft Windows.
+
+ + + + + The specified value is syntactically not a + character encoding name. + +
The attribute value must be a character encoding name. However, + the specified value is not a character encoding name syntactically. + The document is non‐conforming.
+
Character encoding name is a string of ASCII + printable characters, up to 40 characters.
+ + + This attribute only allow a limited set of @@ -830,8 +1110,8 @@

HTML meta element, http-equiv attribute
-
Only Default-Style and Refresh - is allowed.
+
Only values Default-Style and Refresh + are allowed.

Value Content-Type is obsolete; for charset declaration, the charset attribute can be used as:
<meta charset="charset-name">
@@ -849,6 +1129,22 @@ + + Character encoding declaration syntax + <meta http-equiv="Content-Type" content="text/html; charset=charset-name"> + is obsolete. + +
Old long character encoding declaration syntax + <meta http-equiv="Content-Type" content="text/html; charset=charset-name"> + is in use. The document is non‐conforming.
+ +
The new character encoding declaration syntax is: +
<meta charset="charset-name">
+
+ + + This identifier has already been @@ -881,21 +1177,35 @@
The specified link type is non-conforming, and therefore the document is non-conforming.
-
+

Link type contents

Use link type index.

Link type copyright

Use link type license.

Link type home

Use link type index.
+
Link type previous
+
Use link type prev.

Link type start

Use link type first.
-
Link type toc
+
Link type toc or top

Use link type index.

+ + Character encoding name $1 + is different from document character encoding + $0. + +
The specified character encoding name is different from + the character encoding of the document. The document + is non‐conforming.
+ + + Browsing context name @@ -933,8 +1243,8 @@
Warning: The data served to the conforming checker might be out of date; it might have already - been accepted or rejected, depending on which the document - might be conforming or non-conforming. See WHATWG Wiki + been accepted or rejected. The document might or might not be + conforming depending on the status. See WHATWG Wiki for the latest information.
@@ -969,7 +1279,7 @@ The document is non-conforming.

For example, the table below is non-conforming: -
<table> + <table> <tbody> <tr><td rowspan=2></td></tr> </tbody> @@ -988,6 +1298,23 @@ class="should" level="s"> {@}: An obsolete subtype is used. + + The specified Internet Media Type is registered with status + of OBSOLETE. + + + Media type text/ecmascript + Media type text/ecmascript is obsoleted in + favor of application/ecmascript. Note that + text/javascript would be better alternative + for many cases. + Media type text/javascript + Media type text/javascript is obsoleted by + IETF with backward incompatible alternate + application/javascript for architectural + purity. Realist may ignore this warning. + + This IRI does not end with a /. + + The IRI does not end with a /. If there is an + authority component in an IRI, a / should be present + instead of empty path component. + + For example, http://www.example.com/ + is preferred to http://www.example.com. + + +Cache Manifest Errors + + + This document is not a cache manifest. + + The specified document is not a cache manifest. + The document is non-conforming. + + An entity labeled as Internet media type + text/cache-manifest must contain a cache manifest. + + A cache manifest must start with a line whose content is + CACHE MANIFEST + (exactly one space character between + CACHE and MANIFEST). + + + + + +Stability Information + + + This element is in the + call for implementation stage. + + The element is in the call for implementation stage. + + Usually, using the element is safe. However, it is a new feature + so that it might not be implemented correctly. If it is found that + the feature is hard or impossible to implement, the feature + might be revised, or in some case it might be dropped. + + Elements defined by Atom 1.0 (IETF Proposed Standard), and XBL 2.0 + (W3C Candidate Recommendation) belong to this class. + + + + + This element is in the last + call for comments stage. + + The element is in the last call for comments stage. + + The element is relatively mature, though the standardization + is not done yet. It may be used for experiments. Since it is a new + feature, it might not be implemented correctly or at all. If it is + found that the feature is hard or impossible to implement, the feature + might be revised or might be dropped. + + Elements defined by Web Forms 2.0 as well as some elements + defined by HTML5 belong to this class. + + + + + This element is documented in a working + draft. + + The element is documented in a working or editor's draft + and not yet completed. + + The element should not be used for any practical purpose. + The feature might be drastically changed later or might be + entirely removed. + + Most of new elements defined by HTML5 belong to this class. + + + + + This element is not part of any + standard the conformance checker knows. + + The element is not part of any standard or draft the conformance + checker is aware of. + + The element should not be used for any practical purpose unless + there is really a standard that defines the element. + + + + Unsupported Messages @@ -1156,12 +1575,6 @@ is not supported; it might or might not be conforming. - - Conformance checking for language tag - is not supported; it might or might not be conforming. - - Conformance checking for media query @@ -1193,14 +1606,68 @@ manakaiIsHTML:0;;XML Document + +Error Levels + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +Level Conforming? Description MUST‐level error Non‐conforming. A violation to a hard requirement of the specification. +The document is non‐conforming. SHOULD‐level error Non‐conforming, but in some case +conforming. A violation to a requirement of the specification. +The violation might be legitimize in some case. Otherwise, +the document is non‐conforming. Warning Conforming. A warning is an advice from the conformance checker to avoid +to solve a problem in a confusing or possibly wrong way. +It does not affect to the conformance of the document, and +may sometimes be inappropriate. Information Conforming. An informational message just provides an additional information +on the feature used in the document or the status of the retrieval +or so on. +It does not affect to the conformance of the document. Not supported Unknown. Some feature that is not supported by the conformance checker +is used in the document. + + License of This Document -Copyright 2007 Wakaba +Copyright 2007‐2008 +Wakaba +<w@suika.fam.cx>. + This document is free software; you can redistribute it and/or modify it under the same terms as Perl itself. - + \ No newline at end of file

Description of Errors

HTML5 Character Encoding Errors

HTML5 Parse Errors in Tokenization Stage

Attribute Value Errors

Cache Manifest Errors

Stability Information

Unsupported Messages

Error Levels

License of This Document

Level	Conforming?	Description
MUST‐level error	Non‐conforming.	A violation to a hard requirement of the specification. +The document is non‐conforming.
SHOULD‐level error	Non‐conforming, but in some case +conforming.	A violation to a requirement of the specification. +The violation might be legitimize in some case. Otherwise, +the document is non‐conforming.
Warning	Conforming.	A warning is an advice from the conformance checker to avoid +to solve a problem in a confusing or possibly wrong way. +It does not affect to the conformance of the document, and +may sometimes be inappropriate.
Information	Conforming.	An informational message just provides an additional information +on the feature used in the document or the status of the retrieval +or so on. +It does not affect to the conformance of the document.
Not supported	Unknown.	Some feature that is not supported by the conformance checker +is used in the document.