--- test/html-webhacc/error-description-source.xml 2007/07/21 04:58:17 1.6 +++ test/html-webhacc/error-description-source.xml 2007/09/04 11:40:02 1.10 @@ -28,6 +28,21 @@ + + Tag <$0> + is not allowed after the end tag </body>. + +

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

+ +

Any content of the document other than head + contents and comments must be put into the body + element.

+
+
+ The & character must @@ -38,6 +53,9 @@ is not part of any reference appears in the input stream. The document is non-conforming.

+

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

+

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

@@ -63,6 +81,29 @@ + + A </ string is not followed + by a tag name. + +

There is a < (U+003C + LESS-THAN SIGN) character + immediately followed by a / (U+005F + SOLIDUS) character, which is not part + of any end tag, in the input stream. The document + is non-conforming.

+ +

The </ sequence immediately followed + by an EOF is + interpreted as a string data of </.

+ +

The </ sequence as string data must + be escaped as: +

&lt;/
+

+
+
+ A < character is not followed @@ -134,6 +175,60 @@ + + String <! is not followed + by --. + +

There is a < (U+003C + LESS-THAN SIGN) character + followed by a ! (U+0021 + EXCLAMATION MARK) character, + which is not followed by a -- or + !DOCTYPE. The document is non-conforming.

+ +
+
Comments
+
In HTML documents, comments must be introduced by + <!-- (<! immediately followed + by two -s) and must be terminated by + -->. 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.
+
Markup declarations
+
Markup declarations, except DOCTYPE + and comment declarations, are not allowed in HTML documents.
+
String <!
+
String <! must be escaped as + &lt;!.
+
+
+
+ + + String </ is not followed + by tag name. + +

There is a < (U+003C + LESS-THAN SIGN) character + immediately followed by a / (U+005F + SOLIDUS) character, which is not part + of any end tag, in the input stream. The document + is non-conforming.

+ +

The </ sequence not followed by a + tag name is parsed as an opening of bogus comment.

+ +

The </ sequence as string data must + be escaped as: +

&lt;/
+

+
+
+ There is a -- sequence @@ -166,19 +261,43 @@ - Void element syntax (/>) cannot be + Polytheistic slash (/>) cannot be used for this element. -

Void element syntax (/>) must not be used +

Polytheistic slash (/>) must not be used for the element. The document is non-conforming.

-

The void element syntax can only be +

The polytheistic slash can only be used for base, link, meta, hr, br, img, embed, param, area, col, and input elements.

-

Note that, unlike in XML, the void element syntax has +

+
<script/>
+

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

+ +

NOTE: Though some user agents interpret + polytheistic slash for script element as the + closing of the element, such usage is not allowed under + the current standard.

+
<basefont/>, <bgsound/>, + <frame/>, <keygen/>, + <spacer/>, <wbr/>
+
These elements are themselves non-conforming.
+ +
<command/>, <event-source/>, + <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.
+
+ +

Note that, unlike in XML, the polytheistic slash has no effect in HTML.

@@ -187,28 +306,35 @@ Processing instruction - (<?...?>) cannot be used. + (<?...>) cannot be used.

Processing instructions (<?...?>), including XML declaration (<?xml ...?>) and XML style sheet PI - (<xml-stylesheet ...?>), are not allowed + (<?xml-stylesheet ...?>), are not allowed in the HTML syntax. The document is non-conforming.

-

If it is necessary to embed a processing instruction - in the HTML document, you must use the XML syntax instead.

- -

In the HTML syntax, XML declaration is not necessary.

- -

Instead of XML style sheet, - PIs, you must - use the HTML link element whose rel - attribute is set to stylesheet (or - alternate stylesheet for an aleternate style sheet).

+
+
<?xml?> (XML declaration)
+
XML declaration is unnecessary for HTML documents.
+
<?xml-stylesheet?> (XML style sheet + PI
+
Use HTML link element with rel + attribute set to stylesheet (or, + alternate stylesheet for an alternate style + sheet).
+
<?php?> (PHP code)
+
The conformance checker does not support + checking for PHP source documents.
+
Other processing instructions
+
Processing instructions cannot be inserted in an HTML + document. Use XML document or insert + ProcessingInstruction node by scripting.
+

Web browsers will parse processing instructions as bogus comments. Some legacy Web browsers, such as IE:mac and - some mobile browsers, will display processing instructions + some mobile Web browsers, will display processing instructions as string.

@@ -258,7 +384,7 @@ Tag <$0> - is not allowed in a body element. + is not allowed in the body element.

The start or end tag of an element, which cannot be a descendant of body element, appears @@ -269,7 +395,7 @@ - Start tag <head> + Start tag <head> is not allowed in the head element.

There is a start tag <head> in the @@ -356,6 +482,18 @@

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.

+ +

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

+ +

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

@@ -479,9 +617,6 @@

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 element with the error is an inline-level element, @@ -492,15 +627,31 @@

Any inline-level content must be put in e.g. paragraph element such as p.

-
If the element with the error is a block-level element, - such as div, hn, or - section
-

Though some elements such as div, - li, and td allow - either one of block-level or inline-level content - is allowed. If there is a block-level content, - any inline-level content must be put - in e.g. paragraph element such as p.

+
If it is a block-level elements, such as aside, + div, hn, + p, or section
+
+
If the parent element is div, + li, td, or th
+ + +

The parent element allows either + block-level or inline-level content. If there is a + block-level content, any inline-level content must be + put in e.g. paragraph element such as p.

+

For example, an HTML document fragment + <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>
+

+
If the parent element does not allow + block-level elements as content
+
The element is not allowed to be inserted here. + For example, a div element cannot be + a child of an h1 element.
+
If the element with the error is a noscript element
The noscript element is allowed only in the context where a block-level or inline-level content is expected @@ -513,6 +664,19 @@ 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, + input, label, + optgroup, option, output, + rb, rp, rt, ruby, + textarea, or textarea element
+ +
These elements are intentionally not supported by the conformance + checker yet.

@@ -545,11 +709,35 @@ 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.

+ cannot provide full functionality of the element to the user.

+ +
+
HTML img element
+
The src attribute must be specified. + Additionally, the alt attribute must be specified + in many cases.
+
HTML link element
+
The rel attribute must be specified. + Note that the rev attribute is obsolete.
+
+ + + + + Attribute + {local-name} is not allowed for + {element-local-name} element. + +

An attribute is specified where it is not allowed. + The document is non-conforming.

+ +
+
HTML meta element
+
For HTML meta element, only one of + name, http-equiv, or charset + attribute is allowed.
+
@@ -557,13 +745,12 @@ class="attribute-error"> 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 lang attribute in the null - namespace for HTML elements is defined as conforming only for - XML document.

+

Use of the xml:lang attribute is conforming + only in XML documents.

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

@@ -604,8 +791,8 @@ XML document. The document is non-conforming.

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

+ namespace for HTML elements is conforming only in + HTML documents.

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

@@ -621,7 +808,7 @@

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

-

This error should not occur in conformance-checking +

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

@@ -636,6 +823,30 @@ This attribute only allow a limited set of values and the specified value {@} is not one of them. + +

For this attribute only several values are allowed and the + value of the attribute is not one of them. The document + is non-conforming.

+ +
+
HTML meta element, http-equiv attribute
+

Only Default-Style and Refresh + is allowed.

+

Value Content-Type is obsolete; for charset + declaration, the charset attribute can be used as: +

<meta charset="charset-name">
+ ... where charset-name is a name of the character encoding + of the document, such as utf-8.

+

Values Content-Style-Type and + Content-Script-Type are currently not allowed.

+

Value Keywords is not allowed. Use + name attribute instead of http-equiv + attribute.

+

Values Expires, Pragma, + and Cache-Control are not allowed; + use real HTTP header fields for cache control.

+
+
<td rowspan=2></td></tr> </tbody> </table> - ... is non-conforming, since the second row contains only - a cell that spans the first and the second rows.

+ ... since the second row contains only + a cell that spans between first and second rows.

@@ -818,13 +1029,13 @@ -
-

URI (or IRI) Warnings

+
+

URI (or IRI) Should-level Errors

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

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

@@ -839,14 +1050,14 @@ - This IRI should explicitly end with - /. + This IRI does not end with + a /. - Hexadecimal digit in percent-encoding - should be in lowercase. + A lowercase hexadecimal digit is used + in percent-encoding.

The hexadecimal digit in percent-encoding string in the IRI is in lowercase. Though the IRI is conforming, @@ -890,31 +1101,34 @@

Unsupported Messages

- - This attribute is not supported by the - conformance checker; it might or might not be conforming. + Conformance checking for element + {local-name} is not supported; it might or + might not be conforming. -

The conformant checker does not support the attribute. +

The conformant checker does not support the element. It cannot determine whether the document is conforming or not.

- - This element is not supported by the - conformance checker; it might or might not be conforming. + Conformance checking for attribute + {local-name} of element + {element-local-name} is not supported; + it might or might not be conforming. -

The conformant checker does not support the element. +

The conformant checker does not support the attribute. It cannot determine whether the document is conforming or not.

- The link type $0 is not + Link type $0 is not standardized or registered at the time of the release of the conformance - checker; it is non-conforming unless it has now been + checker; it is non-conforming unless it now has been registered.

The rel attribute is defined as a list of link types. @@ -927,6 +1141,12 @@ The link type might have been added to the registry since then. In such case it might be conforming. Otherwise, the document is non-conforming.

+ +
+
Link types shortcut icon
+
Link type shortcut is not registered. + Use only icon for linking to so-called favicon.
+
@@ -976,11 +1196,11 @@

License of This Document

-

Copyright 2007 Wakaba

-

This library is free software; you can redistribute it +

Copyright 2007

+

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