--- test/html-webhacc/error-description-source.xml 2007/07/16 08:38:48 1.2 +++ test/html-webhacc/error-description-source.xml 2007/07/16 10:55:11 1.3 @@ -14,12 +14,117 @@

HTML5 Parse Errors in Tokenization Stage

+ + Tag <$0> + is not allowed after the end tag </html>. + +

The start or end tag of an element appears after the + html element has been closed. The document is + non-conforming.

+ +

Any content of the document other than comments + must be put into the html element.

+
+
+ + + The & character must + introduce a reference. + +

An & (U+0026 + AMPERSAND) character which + is not part of any reference appears in the input stream. + The document is non-conforming.

+ +

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

+
Named entity reference
+
&entity-name;
+ where entity-name is the name of the + character entity to be referenced.
+
Numeric character reference
+
&#d;
+ where d is the decimal representation of + the code position of the character to be referenced.
+
Hexadecimal character reference
+
&#xh;
+ where h is the hexadecimal representation + of the code position of the character to be referenced.
+
+

+ +

To represent & as a data character, use + named entity reference: +

&amp;
+

+
+
+ + + The decimal representation of the code position + of a character must be specified after &#. + +

An & (U+0026 + AMPERSAND) character immediately + followed by a # (U+0023 + NUMBER SIGN) character which + is not part of any reference appears in the input stream. + The document is non-conforming.

+ +

The string &# must be the first two characters + NUMBER SIGN) character must be the first two characters + of a reference: +

+
Numeric character reference
+
&#d;
+ where d is the decimal representation of + the code point of the character to be referenced.
+
Hexadecimal character reference
+
&#xh;
+ where h is the hexadecimal representation + of the code point of the character to be referenced.
+
+

+ +

To represent &# as data characters, use + named entity reference: +

&amp;#
+

+
+
+ + + The hexadecimal representation of the code position + of a character must be specified after &#x. + +

The string &#x or &#X which + is not part of any reference appears in the input stream. + The document is non-conforming.

+ +

The string &#x or &#X must + be the first three characters of a hexadecimal reference: +

&#xh;
+ where h is the hexadecimal representation + of the code point of the character to be referenced.

+ +

To represent &#x as data characters, use + named entity reference: +

&amp;#x
+

+
+
+ There are two attributes with same name. -

Attributes must be unique in an element. Specifying - attributes with same name more than once is non-conforming.

+

There are more than one attributes with the same + name in a tag. The document is non-conforming.

The motion attribute is not part of the HTML standard. Use img element with animation GIF instead.

@@ -31,14 +136,16 @@ Void element syntax (/>) cannot be used for this element. -

The void element syntax /> syntax can only be +

Void element syntax (/>) must not be used + for the element. The document is non-conforming.

+ +

The void element syntax can only be used for base, link, meta, hr, br, img, embed, param, area, - col, and input elements. - For any other elements, using that syntax is non-conforming.

+ col, and input elements.

-

Unlike XML, the void element syntax (/>) has +

Note that, unlike in XML, the void element syntax has no effect in HTML.

@@ -53,28 +160,103 @@ The $0 element cannot be inserted between head and body elements. -

A start tag occurs after the head element is closed +

A start tag appears after the head element is closed but before the body element is opened. The document is non-conforming.

+ + Tag <$0> + is not allowed in table. + +

The start or end tag of an element appears in table. + The document is non-conforming.

+ +

In table, only table related elements + are allowed; any other element must be contained in + td or th element to form + a part of the table, or caption element to create + a table caption.

+
+
+ + + Data character is not allowed in + table. + +

A data character appears in table. The document + is non-conforming.

+ +

In table, only table related elements + are allowed; any other element and data character must be contained in + td or th element to form + a part of the table, or caption element to create + a table caption.

+
+
+ + + Start tag of tr + element is missing. + +

Start tag of a tr element, which is not + optional, is missing. The document is non-conforming.

+ +

In a table section, a <tr> start tag + must occur before any <td> or + <th> start tag. Though the HTML5 parser + implies the <tr> start tag before + these start tags, it must be explicitly specified.

+
+
+ This document does not start with the - DOCTYPE declaration. + DOCTYPE. + +

The document does not start with a DOCTYPE. + The document is non-conforming.

+ +

An HTML document must start by a DOCTYPE: +

<!DOCTYPE HTML>
+

+ +

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

+
Element $0 is not closed. + +

End tag of an element is not found before, for example, + an end tag of another element appears or + the end of the document. The document is non-conforming.

+
This document is written in an old version of HTML. + +

The document contains a DOCTYPE declaration + that is different from HTML5 DOCTYPE (i.e. <!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 + specification other than HTML5 provides for no practical + convenience, since Web borwsers will parse any + HTML document (roughly) as defined in HTML5.

+
Data character is not allowed in this context. -

A data character occurs where it is not allowed in this +

A data character appears where it is not allowed in this context. The document is non-conforming.

Possible causes: @@ -126,7 +308,7 @@

The content model of the element is so defined that it must contain a $0 child element. - Without such an element, the document is non-conforming.

+ The document is non-conforming.

For example:

    @@ -146,8 +328,8 @@ or th element as a child of this element.

    The tr element must contain at least one - td or th child element. Without - such an element, the document is non-conforming.

    + td or th child element. The document + is non-conforming.

    @@ -156,9 +338,12 @@ This element is not allowed in this context. -

    An element occurs where it is not allowed. The document +

    An element appears where it is not allowed. The document is non-conforming.

    +

    Note: The conformance checker does + not support form elements yet.

    +

    Possible causes:

    If the erred element is an inline-level element (such @@ -189,20 +374,141 @@
+
+

Attribute Errors

+ + + Required attribute $0 + is not specified. + +

A required attribute is not specified. The document + is non-conforming.

+ +

Some attribute is defined as required. + For example, any img element must have + alt and src attributes specified. + Without required attributes specified, user agents + cannot provide the full functionality of the element + to the user.

+
+
+ + + The xml:lang attribute is not + allowed in HTML document. + +

The xml:lang attribute is not allowed in + HTML document. The document is non-conforming.

+ +

The xml:lang attribute in null + namespace for HTML elements is defined as conforming only for + XML document.

+ +

To specify natural language information in HTML document, + use lang attribute instead.

+ +
+
+ + + The charset attribute is not + allowed in XML document. + +

The charset attribute of a + meta element is not allowed in XML document. + The document is non-conforming.

+ +

To specify the character encoding used for serialization, + if necessary, use XML declaration instead: +

<?xml version="1.0" encoding="encoding-name"?>
+

+
+
+ + + The lang attribute is not + allowed in XML document. + +

The HTML lang attribute is not allowed in + XML document. The document is non-conforming.

+ +

The lang attribute in null + namespace for HTML elements is defined as conforming only for + HTML document.

+ +

To specify natural language information in XML document, + use xml:lang attribute instead.

+
+
+ + + The xmlns attribute + in the null namespace is not allowed in + XHTML document. The document is non-conforming. + +

The xmlns attribute in the null + namespace is not allowed in XHTML document.

+ +

This error should not occur in conformance-checking + static documents.

+
+
+ +
+

Attribute Value Errors

+ class="attribute-value-error"> This attribute only allow a limited set of values and the specified value is not one of them. + + This identifier has already been + assigned to another element. + + + + + This browsing context name is reserved. + +

The specified browsing context name is reserved. + The document is non-conforming.

+ +

Names of browsing contexts starting with _ + (U+005F LOW LINE) + are reserved so that it must not be used.

+ +

Old version of HTML, non-HTML markup languages, and + Web browsers define or implements special reserved + browsing context names _blank, + _main, and _replace. + However, they are not conforming attribute values.

+
+
+

Table Model Errors

+ + This colspan attribute + results in creating a table column that does not contain + any cell anchored to it. + + The table has no cell (td or @@ -243,8 +549,24 @@
-
-

URI (or IRI) Errors

+
+

URI (or IRI) Warnings

+ + + Dot-segment (. or + ..) should not occur in an absolute reference. + +

Dot-segment (. or ..) should + not occur in an absolute reference.

+ +

In relative references, dot-segments are used to represent + the current (.) or the parent (..) + hierarchy of the path. Though they are also allowed + in absolute references, it should be resolved to the + canonical form before it has been published.

+
+
@@ -315,6 +637,6 @@ and/or modify it under the same terms as Perl itself.

- + \ No newline at end of file