- From: poot <cvsmail@w3.org>
- Date: Sun, 30 Nov 2008 07:30:56 +0900 (JST)
- To: public-html-diffs@w3.org
Experimental attempt at listing a set of errors that validators can
comfortably classify as lower priority to aid transition. (whatwg r2476)
applets
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1647.html#dom-document-applets
8.2.5.4 The "initial" insertion mode
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1647.html#the-initial-insertion-mode
10.2 Conformance checkers
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1647.html#conformance-checkers-0
DOCTYPE parse error
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1647.html#doctype-parse-error
11 Things that you can't do with this specification because they are better handled using other technologies that are further described herein
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1647.html#no
http://people.w3.org/mike/diffs/html5/spec/Overview.diff.html
http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.1646&r2=1.1647&f=h
http://html5.org/tools/web-apps-tracker?from=2475&to=2476
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.1646
retrieving revision 1.1647
diff -u -d -r1.1646 -r1.1647
--- Overview.html 29 Nov 2008 21:59:33 -0000 1.1646
+++ Overview.html 29 Nov 2008 22:28:07 -0000 1.1647
@@ -913,7 +913,8 @@
<li><a href=#obsolete-elements><span class=secno>10.1 </span>Obsolete elements</a>
<ol>
<li><a href=#the-body-element-0><span class=secno>10.1.1 </span>The <code>body</code> element</a></li>
- <li><a href=#the-applet-element><span class=secno>10.1.2 </span>The <code>applet</code> element</a></ol></ol></li>
+ <li><a href=#the-applet-element><span class=secno>10.1.2 </span>The <code>applet</code> element</a></ol></li>
+ <li><a href=#conformance-checkers-0><span class=secno>10.2 </span>Conformance checkers</a></ol></li>
<li><a href=#no><span class=secno>11 </span>Things that you can't do with this specification because
they are better handled using other technologies that are further
described herein</a>
@@ -38214,13 +38215,13 @@
<p>If the DOCTYPE token's <code title="">name</code> is not an
<a href=#ascii-case-insensitive>ASCII case-insensitive</a> match for the string "<code title="">HTML</code>", or if the token's public identifier is
neither missing nor equal to the string
- "<code>XSLT-compat</code>", or if the token's system identifier
- is not missing, then there is a <a href=#parse-error>parse
- error</a>. Conformance checkers may, instead of reporting this
- error, switch to a conformance checking mode for another language
- (e.g. based on the DOCTYPE token a conformance checker could
- recognize that the document is an HTML4-era document, and defer to
- an HTML4 conformance checker.)</p>
+ "<code>XSLT-compat</code>", or if the token's system identifier is
+ not missing, then there is a <a href=#parse-error>parse error</a> (this is the
+ <dfn id=doctype-parse-error>DOCTYPE parse error</dfn>). Conformance checkers may, instead
+ of reporting this error, switch to a conformance checking mode for
+ another language (e.g. based on the DOCTYPE token a conformance
+ checker could recognize that the document is an HTML4-era
+ document, and defer to an HTML4 conformance checker.)</p>
<p>Append a <code>DocumentType</code> node to the
<code>Document</code> node, with the <code title="">name</code>
@@ -43905,7 +43906,49 @@
};</pre><p>The <dfn id=dom-document-applets title=dom-document-applets><code>applets</code></dfn>
attribute must return an <code><a href=#htmlcollection-0>HTMLCollection</a></code> rooted at the
<code>Document</code> node, whose filter matches only
- <code><a href=#the-applet-element>applet</a></code> elements.<h2 id=no><span class=secno>11 </span>Things that you can't do with this specification because
+ <code><a href=#the-applet-element>applet</a></code> elements.<h3 id=conformance-checkers-0><span class=secno>10.2 </span>Conformance checkers</h3><p>To ease the transition from HTML4 Transitional documents to the
+ language defined in <em>this</em> specification, conformance
+ checkers are encouraged to categorise errors that represent usage of
+ old obsolete features that generally have no effect (as defined
+ below) into a separate part of their report, to allow authors to
+ distinguish between likely mistakes and mere vestigial markup.<p>The following errors may be categorised as described above:<ul><li>
+
+ <p>The <a href=#doctype-parse-error>DOCTYPE parse error</a>, if the DOCTYPE token's
+ <code title="">name</code> is an <a href=#ascii-case-insensitive>ASCII
+ case-insensitive</a> match for the string "<code title="">HTML</code>", and either:</p>
+
+ <ul><li>the token's public identifier is the
+ <a href=#case-sensitive>case-sensitive</a> string "<code title="">-//W3C//DTD HTML 4.0//EN</code>" and the
+ token's system identifier is either missing or the
+ <a href=#case-sensitive>case-sensitive</a> string "<code title="">http://www.w3.org/TR/REC-html40/strict.dtd</code>", or</li>
+
+ <li>the token's public identifier is the
+ <a href=#case-sensitive>case-sensitive</a> string "<code title="">-//W3C//DTD HTML 4.01//EN</code>" and the
+ token's system identifier is either missing or the
+ <a href=#case-sensitive>case-sensitive</a> string "<code title="">http://www.w3.org/TR/html4/strict.dtd</code>", or</li>
+
+ <li>the token's public identifier is the
+ <a href=#case-sensitive>case-sensitive</a> string "<code title="">-//W3C//DTD XHTML 1.0 Strict//EN</code>"
+ and the token's system identifier is either missing or the
+ <a href=#case-sensitive>case-sensitive</a> string "<code title="">http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd</code>",
+ or</li>
+
+ <li>the token's public identifier is the
+ <a href=#case-sensitive>case-sensitive</a> string "<code title="">-//W3C//DTD XHTML 1.1//EN</code>"
+ and the token's system identifier is either missing or the
+ <a href=#case-sensitive>case-sensitive</a> string "<code title="">http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd</code>".</li>
+
+ </ul><!-- only things that trigger no-quirks mode and were valid in
+ some other spec are allowed in this list --></li>
+
+ <li><p>The presence of a <code title=attr-img-border>border</code> attribute on an
+ <code><a href=#the-img-element>img</a></code> element if its value is the string "<code title="">0</code>".</li>
+
+ <li><p>The presence of a <code title=attr-script-language></code>
+ attribute on a <code><a href=#script>script</a></code> element if its value is an
+ <a href=#ascii-case-insensitive>ASCII case-insensitive</a> match for the string "<code title="">JavaScript</code>".</li>
+
+ </ul><h2 id=no><span class=secno>11 </span>Things that you can't do with this specification because
they are better handled using other technologies that are further
described herein</h2><p><em>This section is non-normative.</em><p>There are certain features that are not handled by this
specification because a client side markup language is not the right
Received on Saturday, 29 November 2008 22:31:43 UTC