--- 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 @@
+ The start or end tag of an element appears after the
+ Any content of the document other than <$0>
+ is not allowed after the end tag </body>.body element has been closed. The document is
+ non-conforming.head
+ contents and comments must be put into the body
+ element.& 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 &.
The & character must
be the first character of a reference:
</ 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:
+
</
+
+ < character is not followed
@@ -134,6 +175,60 @@
<! 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.
<!-- (<! 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.CDATA sectionsDOCTYPE
+ and comment declarations, are not allowed in HTML documents.<!<! must be escaped as
+ <!.</ 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:
+
</
+
+ -- sequence
@@ -166,19 +261,43 @@
/>) cannot be
+ />) 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/><command/>, <event-source/>,
+ <source/><a/>, <p/>Note that, unlike in XML, the polytheistic slash has no effect in HTML.
<?...?>) 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-stylesheet?> (XML style sheet
+ PIlink element with rel
+ attribute set to stylesheet (or,
+ alternate stylesheet for an alternate style
+ sheet).<?php?> (PHP code)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.
<$0>
- is not allowed in a body element.body element.
The start or end tag of an element, which
cannot be a descendant of There is a start tag 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 Note that misnesting tags, such as
+ body element, appears
@@ -269,7 +395,7 @@
<head>
+ <head>
is not allowed in the head element.<head> in the
@@ -356,6 +482,18 @@
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.<a><b></a></b>, are not
+ allowed and they also cause this error.
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:
Any inline-level content must be put
in e.g. paragraph element such as p.
div, hn, or
- sectionThough 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.
aside,
+ div, hn,
+ p, or sectiondiv,
+ li, td, or thThe 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>
+ div element cannot be
+ a child of an h1 element.noscript elementnoscript 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.blink,
+ center, or marquee elementbutton, datalist, form,
+ input, label,
+ optgroup, option, output,
+ rb, rp, rt, ruby,
+ textarea, or textarea elementSome 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.
img elementsrc attribute must be specified.
+ Additionally, the alt attribute must be specified
+ in many cases.link elementrel attribute must be specified.
+ Note that the rev attribute is obsolete.{local-name} is not allowed for
+ {element-local-name} element.An attribute is specified where it is not allowed. + The document is non-conforming.
+ +meta elementmeta element, only one of
+ name, http-equiv, or charset
+ attribute is allowed.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.
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.
This error should not occur in conformance-checking +
This error should not occur in conformance-checking of static documents.
{@} 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.
+ +meta element, http-equiv attributeOnly 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.
. or
- ..) should not occur in an absolute reference.. or
+ ..) occurs in an absolute reference.Dot-segment (. or ..) should
not occur in an absolute reference.
/./.The hexadecimal digit in percent-encoding string in the IRI
is in lowercase. Though the IRI is conforming,
@@ -890,31 +1101,34 @@
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. 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 Copyright 2007 Wakaba This library is free software; you can redistribute it
+ Copyright 2007 Wakaba This document is free software; you can redistribute it
and/or modify it under the same terms as Perl itself.Unsupported Messages
-{local-name} is not supported; it might or
+ might not be conforming.{local-name} of element
+ {element-local-name} is not supported;
+ it might or might not be conforming.$0 is not
+ $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.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.
+
shortcut iconshortcut is not registered.
+ Use only icon for linking to so-called favicon.License of This Document
-