[html5] r46 - This draft is now obsolete.

whatwg at whatwg.org whatwg at whatwg.org
Mon Jan 5 03:07:55 PST 2009


Author: ianh
Date: 2009-01-05 03:07:55 -0800 (Mon, 05 Jan 2009)
New Revision: 46

Modified:
   header-whatwg
   index
Log:
This draft is now obsolete.

Modified: header-whatwg
===================================================================
--- header-whatwg	2006-10-12 00:56:43 UTC (rev 45)
+++ header-whatwg	2009-01-05 11:07:55 UTC (rev 46)
@@ -11,6 +11,10 @@
    .applies .deprecated { background: #EEEEEE; }
    .applies .deprecated .yes { background: #DDDD99; }
    img { max-width: 100%; }
+   * { color: gray ! important; background: none ! important; border-color: silver ! important; }
+   .obsolete { border: double thick red ! important; background: yellow ! important; margin: 4em 14em 4em 3em; text-align: center; }
+   .obsolete a { color: blue ! important; }
+   .obsolete p { font: 900 2em sans-serif; color: red ! important; margin: 1em 1.5em ! important; }
   </style>
  </head>
  <body class="draft">
@@ -19,6 +23,14 @@
    <p><a rel="home" href="http://www.whatwg.org/" class="logo"><img alt="WHATWG" src="/images/logo"></a></p>
    <h1>Web Forms 2.0</h1>
    <h2 class="no-num no-toc">Working Draft — [DATE: 01 Jan 1901]</h2>
+
+   <div class="obsolete">
+    <p>This draft has been superseded by the Forms chapter of the <a
+    href="http://whatwg.org/html5">HTML5 specification</a>, which now
+    includes many of the features first defined in this document.</p>
+    <p>This document will not be further updated.</p>
+   </div>
+
    <dl>
     <dt>This version:</dt>
     <dd><a href="http://www.whatwg.org/specs/web-forms/current-work/">http://www.whatwg.org/specs/web-forms/current-work/</a></dd>

Modified: index
===================================================================
--- index	2006-10-12 00:56:43 UTC (rev 45)
+++ index	2009-01-05 11:07:55 UTC (rev 46)
@@ -13,6 +13,10 @@
    .applies .deprecated { background: #EEEEEE; }
    .applies .deprecated .yes { background: #DDDD99; }
    img { max-width: 100%; }
+   * { color: gray ! important; background: none ! important; border-color: silver ! important; }
+   .obsolete { border: double thick red ! important; background: yellow ! important; margin: 4em 14em 4em 3em; text-align: center; }
+   .obsolete a { color: blue ! important; }
+   .obsolete p { font: 900 2em sans-serif; color: red ! important; margin: 1em 1.5em ! important; }
   </style>
 
  <body class=draft>
@@ -20,10 +24,18 @@
    <p><a class=logo href="http://www.whatwg.org/" rel=home><img alt=WHATWG
     src="/images/logo"></a></p>
 
-   <h1 id=web-forms>Web Forms 2.0</h1>
+   <h1>Web Forms 2.0</h1>
 
-   <h2 class="no-num no-toc" id=working>Working Draft — 12 October 2006</h2>
+   <h2 class="no-num no-toc" id=working>Working Draft — 5 January 2009</h2>
 
+   <div class=obsolete>
+    <p>This draft has been superseded by the Forms chapter of the <a
+     href="http://whatwg.org/html5">HTML5 specification</a>, which now
+     includes many of the features first defined in this document.</p>
+
+    <p>This document will not be further updated.</p>
+   </div>
+
    <dl>
     <dt>This version:
 
@@ -128,170 +140,167 @@
   <ul class=toc>
    <li><a href="#introduction"><span class=secno>1. </span>Introduction</a>
     <ul class=toc>
-     <li><a href="#scope"><span class=secno>1.1. </span>Scope</a>
+     <li><a href="#scope"><span class=secno>1.1 </span>Scope</a>
 
-     <li><a href="#r-to-html"><span class=secno>1.2. </span>Relationship to
+     <li><a href="#r-to-html"><span class=secno>1.2 </span>Relationship to
       HTML4</a>
 
-     <li><a href="#r-to-xhtml"><span class=secno>1.3. </span>Relationship to
+     <li><a href="#r-to-xhtml"><span class=secno>1.3 </span>Relationship to
       XHTML1.x</a>
 
-     <li><a href="#r-to-html5"><span class=secno>1.4. </span>Relationship to
+     <li><a href="#r-to-html5"><span class=secno>1.4 </span>Relationship to
       HTML5</a>
 
-     <li><a href="#r-to-dom"><span class=secno>1.5. </span>Relationship to
-      the W3C DOM</a>
+     <li><a href="#r-to-dom"><span class=secno>1.5 </span>Relationship to the
+      W3C DOM</a>
 
-     <li><a href="#r-to-xforms"><span class=secno>1.6. </span>Relationship to
+     <li><a href="#r-to-xforms"><span class=secno>1.6 </span>Relationship to
       XForms</a>
 
-     <li><a href="#r-to-css"><span class=secno>1.7. </span>Relationship to
+     <li><a href="#r-to-css"><span class=secno>1.7 </span>Relationship to
       CSS</a>
 
-     <li><a href="#missing"><span class=secno>1.8. </span>Missing
-      features</a>
+     <li><a href="#missing"><span class=secno>1.8 </span>Missing features</a>
+      
 
-     <li><a href="#conformance"><span class=secno>1.9. </span>Conformance
+     <li><a href="#conformance"><span class=secno>1.9 </span>Conformance
       requirements</a>
 
-     <li><a href="#terminology"><span class=secno>1.10.
-      </span>Terminology</a>
+     <li><a href="#terminology"><span class=secno>1.10 </span>Terminology</a>
+      
 
-     <li><a href="#extensibility"><span class=secno>1.11.
+     <li><a href="#extensibility"><span class=secno>1.11
       </span>Extensibility</a>
 
-     <li><a href="#security"><span class=secno>1.12. </span>Security</a>
+     <li><a href="#security"><span class=secno>1.12 </span>Security</a>
     </ul>
 
    <li><a href="#extend-form-controls"><span class=secno>2. </span>Extensions
     to form control elements</a>
     <ul class=toc>
-     <li><a href="#introduction0"><span class=secno>2.1. </span>Introduction
+     <li><a href="#introduction0"><span class=secno>2.1 </span>Introduction
       for authors</a>
 
-     <li><a href="#existing"><span class=secno>2.2. </span>Existing
+     <li><a href="#existing"><span class=secno>2.2 </span>Existing
       controls</a>
 
-     <li><a href="#changes"><span class=secno>2.3. </span>Changes to existing
+     <li><a href="#changes"><span class=secno>2.3 </span>Changes to existing
       controls</a>
 
-     <li><a href="#extensions"><span class=secno>2.4. </span>Extensions to
-      the <code>input</code> element</a>
+     <li><a href="#extensions"><span class=secno>2.4 </span>Extensions to the
+      <code>input</code> element</a>
       <ul class=toc>
-       <li><a href="#ranges"><span class=secno>2.4.1. </span>Ranges</a>
+       <li><a href="#ranges"><span class=secno>2.4.1 </span>Ranges</a>
 
-       <li><a href="#precision"><span class=secno>2.4.2. </span>Precision</a>
-        
+       <li><a href="#precision"><span class=secno>2.4.2 </span>Precision</a>
       </ul>
 
-     <li><a href="#extensions0"><span class=secno>2.5. </span>Extensions to
+     <li><a href="#extensions0"><span class=secno>2.5 </span>Extensions to
       existing attributes</a>
 
-     <li><a href="#the-pattern"><span class=secno>2.6. </span>The
+     <li><a href="#the-pattern"><span class=secno>2.6 </span>The
       <code>pattern</code> attribute</a>
 
-     <li><a href="#the-required"><span class=secno>2.7. </span>The
+     <li><a href="#the-required"><span class=secno>2.7 </span>The
       <code>required</code> attribute</a>
 
-     <li><a href="#formAttribute"><span class=secno>2.8. </span>The <dfn
-      id=form title=form-attribute><code>form</code></dfn> attribute</a>
+     <li><a href="#formAttribute"><span class=secno>2.8 </span>The
+      <code>form</code> attribute</a>
 
-     <li><a href="#the-autocomplete"><span class=secno>2.9. </span>The
+     <li><a href="#the-autocomplete"><span class=secno>2.9 </span>The
       <code>autocomplete</code> attribute</a>
 
-     <li><a href="#the-autofocus"><span class=secno>2.10. </span>The <dfn
-      id=autofocus><code>autofocus</code></dfn> attribute</a>
+     <li><a href="#the-autofocus"><span class=secno>2.10 </span>The
+      <code>autofocus</code> attribute</a>
 
-     <li><a href="#the-inputmode"><span class=secno>2.11. </span>The
+     <li><a href="#the-inputmode"><span class=secno>2.11 </span>The
       <code>inputmode</code> attribute</a>
 
-     <li><a href="#the-datalist"><span class=secno>2.12. </span>The
+     <li><a href="#the-datalist"><span class=secno>2.12 </span>The
       <code>datalist</code> element and the <code>list</code> attribute</a>
 
-     <li><a href="#the-output"><span class=secno>2.13. </span>The <dfn
-      id=output><code>output</code></dfn> element</a>
+     <li><a href="#the-output"><span class=secno>2.13 </span>The
+      <code>output</code> element</a>
 
-     <li><a href="#extensions1"><span class=secno>2.14. </span>Extensions to
+     <li><a href="#extensions1"><span class=secno>2.14 </span>Extensions to
       the <code>textarea</code> element</a>
 
-     <li><a href="#upload"><span class=secno>2.15. </span>Extensions to file
+     <li><a href="#upload"><span class=secno>2.15 </span>Extensions to file
       upload controls</a>
 
-     <li><a href="#extensions2"><span class=secno>2.16. </span>Extensions to
+     <li><a href="#extensions2"><span class=secno>2.16 </span>Extensions to
       the <code>form</code> element</a>
 
-     <li><a href="#extensions3"><span class=secno>2.17. </span>Extensions to
+     <li><a href="#extensions3"><span class=secno>2.17 </span>Extensions to
       the submit buttons</a>
 
-     <li><a href="#handling"><span class=secno>2.18. </span>Handling
+     <li><a href="#handling"><span class=secno>2.18 </span>Handling
       unexpected elements and values</a>
     </ul>
 
    <li><a href="#repeatingFormControls"><span class=secno>3. </span>The
     repetition model for repeating form controls</a>
     <ul class=toc>
-     <li><a href="#introduction1"><span class=secno>3.1. </span>Introduction
+     <li><a href="#introduction1"><span class=secno>3.1 </span>Introduction
       for authors</a>
       <ul class=toc>
-       <li><a href="#more-features"><span class=secno>3.1.1. </span>More
+       <li><a href="#more-features"><span class=secno>3.1.1 </span>More
         features</a>
 
-       <li><a href="#suggestions"><span class=secno>3.1.2. </span>Suggestions
+       <li><a href="#suggestions"><span class=secno>3.1.2 </span>Suggestions
         for authors</a>
 
-       <li><a href="#tracking"><span class=secno>3.1.3. </span>Tracking the
+       <li><a href="#tracking"><span class=secno>3.1.3 </span>Tracking the
         order of repetition blocks in the submission</a>
 
-       <li><a href="#what-the"><span class=secno>3.1.4. </span>What the
+       <li><a href="#what-the"><span class=secno>3.1.4 </span>What the
         repetition model can't do</a>
 
-       <li><a href="#small"><span class=secno>3.1.5. </span>Small example for
+       <li><a href="#small"><span class=secno>3.1.5 </span>Small example for
         non-XHTML documents</a>
       </ul>
 
-     <li><a href="#definitions"><span class=secno>3.2. </span>Definitions</a>
-      
+     <li><a href="#definitions"><span class=secno>3.2 </span>Definitions</a>
       <ul class=toc>
-       <li><a href="#repetition"><span class=secno>3.2.1. </span>Repetition
+       <li><a href="#repetition"><span class=secno>3.2.1 </span>Repetition
         templates</a>
 
-       <li><a href="#repetition0"><span class=secno>3.2.2. </span>Repetition
+       <li><a href="#repetition0"><span class=secno>3.2.2 </span>Repetition
         blocks</a>
       </ul>
 
-     <li><a href="#new-form"><span class=secno>3.3. </span>New form
+     <li><a href="#new-form"><span class=secno>3.3 </span>New form
       controls</a>
 
-     <li><a href="#the-repeat-min"><span class=secno>3.4. </span>The
+     <li><a href="#the-repeat-min"><span class=secno>3.4 </span>The
       <code>repeat-min</code> and <code>repeat-max</code> attributes</a>
 
-     <li><a href="#event"><span class=secno>3.5. </span>Event interface for
+     <li><a href="#event"><span class=secno>3.5 </span>Event interface for
       repetition events</a>
 
-     <li><a href="#repetitionModel"><span class=secno>3.6. </span>The
+     <li><a href="#repetitionModel"><span class=secno>3.6 </span>The
       repetition model</a>
       <ul class=toc>
-       <li><a href="#addition"><span class=secno>3.6.1. </span>Addition</a>
+       <li><a href="#addition"><span class=secno>3.6.1 </span>Addition</a>
 
-       <li><a href="#removal"><span class=secno>3.6.2. </span>Removal</a>
+       <li><a href="#removal"><span class=secno>3.6.2 </span>Removal</a>
 
-       <li><a href="#movement"><span class=secno>3.6.3. </span>Movement of
+       <li><a href="#movement"><span class=secno>3.6.3 </span>Movement of
         repetition blocks</a>
 
-       <li><a href="#initial"><span class=secno>3.6.4. </span>Initial
+       <li><a href="#initial"><span class=secno>3.6.4 </span>Initial
         repetition blocks</a>
 
-       <li><a href="#notes"><span class=secno>3.6.5. </span>Notes for
+       <li><a href="#notes"><span class=secno>3.6.5 </span>Notes for
         assistive technologies</a>
       </ul>
 
-     <li><a href="#repeatExamples"><span class=secno>3.7. </span>Examples</a>
-      
+     <li><a href="#repeatExamples"><span class=secno>3.7 </span>Examples</a>
       <ul class=toc>
-       <li><a href="#repeatExample"><span class=secno>3.7.1. </span>Repeated
+       <li><a href="#repeatExample"><span class=secno>3.7.1 </span>Repeated
         rows</a>
 
-       <li><a href="#nested"><span class=secno>3.7.2. </span>Nested
+       <li><a href="#nested"><span class=secno>3.7.2 </span>Nested
         repeats</a>
       </ul>
     </ul>
@@ -299,69 +308,69 @@
    <li><a href="#forms-events-model"><span class=secno>4. </span>The forms
     event model</a>
     <ul class=toc>
-     <li><a href="#the-click"><span class=secno>4.1. </span>The
+     <li><a href="#the-click"><span class=secno>4.1 </span>The
       <code>click</code> event and <code>input</code> controls</a>
 
-     <li><a href="#the-change"><span class=secno>4.2. </span>The
+     <li><a href="#the-change"><span class=secno>4.2 </span>The
       <code>change</code> and <code>input</code> events</a>
 
-     <li><a href="#events"><span class=secno>4.3. </span>Events to enable
+     <li><a href="#events"><span class=secno>4.3 </span>Events to enable
       simpler dependency tracking</a>
 
-     <li><a href="#form-validation"><span class=secno>4.4. </span>Form
+     <li><a href="#form-validation"><span class=secno>4.4 </span>Form
       validation</a>
 
-     <li><a href="#receiving"><span class=secno>4.5. </span>Receiving the
+     <li><a href="#receiving"><span class=secno>4.5 </span>Receiving the
       results of form submission</a>
 
-     <li><a href="#the-domcontrolvaluechanged"><span class=secno>4.6.
+     <li><a href="#the-domcontrolvaluechanged"><span class=secno>4.6
       </span>The <code>DOMControlValueChanged</code> event</a>
     </ul>
 
    <li><a href="#form-submission"><span class=secno>5. </span>Form
     submission</a>
     <ul class=toc>
-     <li><a href="#successful"><span class=secno>5.1. </span>Successful form
+     <li><a href="#successful"><span class=secno>5.1 </span>Successful form
       controls</a>
 
-     <li><a href="#unacceptableCharacters"><span class=secno>5.2.
+     <li><a href="#unacceptableCharacters"><span class=secno>5.2
       </span>Handling characters outside the submission character
       encoding</a>
       <ul class=toc>
-       <li><a href="#the-charset"><span class=secno>5.2.1. </span>The <dfn
-        id=charset><code>_charset_</code></dfn> control</a>
+       <li><a href="#the-charset"><span class=secno>5.2.1 </span>The
+        <code>_charset_</code> control</a>
       </ul>
 
-     <li><a href="#x-www-form-urlencoded"><span class=secno>5.3.
+     <li><a href="#x-www-form-urlencoded"><span class=secno>5.3
       </span><code>application/x-www-form-urlencoded</code></a>
 
-     <li><a href="#x-www-form-xml"><span class=secno>5.4.
+     <li><a href="#x-www-form-xml"><span class=secno>5.4
       </span><code>application/x-www-form+xml</code>: XML submission</a>
 
-     <li><a href="#text-plain"><span class=secno>5.5.
+     <li><a href="#text-plain"><span class=secno>5.5
       </span><code>text/plain</code></a>
 
-     <li><a href="#methodAndEnctypes"><span class=secno>5.6.
+     <li><a href="#methodAndEnctypes"><span class=secno>5.6
       </span><!--Semantics of <code>method</code> and
   <code>enctype</code> attributes: -->Submitting
       the encoded form data set</a>
       <ul class=toc>
-       <li><a href="#for-http"><span class=secno>5.6.1. </span>For
+       <li><a href="#for-http"><span class=secno>5.6.1 </span>For
         <code>http:</code> actions</a>
 
-       <li><a href="#for-ftp"><span class=secno>5.6.2. </span>For
+       <li><a href="#for-ftp"><span class=secno>5.6.2 </span>For
         <code>ftp:</code> actions</a>
 
-       <li><a href="#for-data"><span class=secno>5.6.3. </span>For
+       <li><a href="#for-data"><span class=secno>5.6.3 </span>For
         <code>data:</code> actions</a>
 
-       <li><a href="#for-file"><span class=secno>5.6.4. </span>For
+       <li><a href="#for-file"><span class=secno>5.6.4 </span>For
         <code>file:</code> actions</a>
 
-       <li><a href="#for-mailto"><span class=secno>5.6.5. </span>For
+       <li><a href="#for-mailto"><span class=secno>5.6.5 </span>For
         <code>mailto:</code> actions</a>
 
-       <li><a href="#for-javascript"><span class=secno>5.6.6. </span>For
+       <li><a href="#for-javascript"><span class=secno>5.6.6 </span>For
         <code>javascript:</code> actions</a>
       </ul>
     </ul>
@@ -369,68 +378,68 @@
    <li><a href="#fetching-data"><span class=secno>6. </span>Fetching data
     from external resources</a>
     <ul class=toc>
-     <li><a href="#selectSeeding"><span class=secno>6.1. </span>Filling
+     <li><a href="#selectSeeding"><span class=secno>6.1 </span>Filling
       <code>select</code> elements</a>
 
-     <li><a href="#seeding"><span class=secno>6.2. </span>Seeding a form with
+     <li><a href="#seeding"><span class=secno>6.2 </span>Seeding a form with
       initial values</a>
     </ul>
 
    <li><a href="#dom"><span class=secno>7. </span>Extensions to the HTML
     Level 2 DOM interfaces</a>
     <ul class=toc>
-     <li><a href="#additions"><span class=secno>7.1. </span>Additions
-      specific to the <code>HTMLFormElement</code> interface</a>
+     <li><a href="#additions"><span class=secno>7.1 </span>Additions specific
+      to the <code>HTMLFormElement</code> interface</a>
 
-     <li><a href="#additions0"><span class=secno>7.2. </span>Additions
+     <li><a href="#additions0"><span class=secno>7.2 </span>Additions
       specific to the <code>HTMLSelectElement</code> interface</a>
 
-     <li><a href="#the-htmldatalistelement"><span class=secno>7.3. </span>The
+     <li><a href="#the-htmldatalistelement"><span class=secno>7.3 </span>The
       <code>HTMLDataListElement</code> interface</a>
 
-     <li><a href="#changes0"><span class=secno>7.4. </span>Changes to the
+     <li><a href="#changes0"><span class=secno>7.4 </span>Changes to the
       <code>HTMLOptionElement</code> interface</a>
 
-     <li><a href="#additions1"><span class=secno>7.5. </span>Additions
+     <li><a href="#additions1"><span class=secno>7.5 </span>Additions
       specific to the <code>HTMLFieldsetElement</code> interface</a>
 
-     <li><a href="#the-htmloutputelement"><span class=secno>7.6. </span>The
+     <li><a href="#the-htmloutputelement"><span class=secno>7.6 </span>The
       <code>HTMLOutputElement</code> interface</a>
 
-     <li><a href="#validation"><span class=secno>7.7. </span>Validation
+     <li><a href="#validation"><span class=secno>7.7 </span>Validation
       APIs</a>
 
-     <li><a href="#new-dom"><span class=secno>7.8. </span>New DOM attributes
+     <li><a href="#new-dom"><span class=secno>7.8 </span>New DOM attributes
       for new content attributes</a>
 
-     <li><a href="#additions2"><span class=secno>7.9. </span>Additions
+     <li><a href="#additions2"><span class=secno>7.9 </span>Additions
       specific to the <code>HTMLInputElement</code> interface</a>
 
-     <li><a href="#the-defaultvalue"><span class=secno>7.10. </span>The
+     <li><a href="#the-defaultvalue"><span class=secno>7.10 </span>The
       <code>defaultValue</code> DOM attribute</a>
 
-     <li><a href="#labels"><span class=secno>7.11. </span>Labels</a>
+     <li><a href="#labels"><span class=secno>7.11 </span>Labels</a>
 
-     <li><a href="#firing"><span class=secno>7.12. </span>Firing change
+     <li><a href="#firing"><span class=secno>7.12 </span>Firing change
       events</a>
 
-     <li><a href="#repetition1"><span class=secno>7.13. </span>Repetition
+     <li><a href="#repetition1"><span class=secno>7.13 </span>Repetition
       interfaces</a>
     </ul>
 
    <li><a href="#presentation"><span class=secno>8. </span>Presentation and
     rendering</a>
     <ul class=toc>
-     <li><a href="#styling-form-controls"><span class=secno>8.1.
+     <li><a href="#styling-form-controls"><span class=secno>8.1
       </span>Styling form controls</a>
 
-     <li><a href="#relation"><span class=secno>8.2. </span>Relation to CSS
+     <li><a href="#relation"><span class=secno>8.2 </span>Relation to CSS
       selectors</a>
 
-     <li><a href="#interaction"><span class=secno>8.3. </span>Interaction of
+     <li><a href="#interaction"><span class=secno>8.3 </span>Interaction of
       the form processing model with CSS</a>
 
-     <li><a href="#interaction0"><span class=secno>8.4. </span>Interaction of
+     <li><a href="#interaction0"><span class=secno>8.4 </span>Interaction of
       the form processing model with SMIL</a>
     </ul>
 
@@ -502,7 +511,7 @@
    specifications for the definitions of features that this specification
    does not change.
 
-  <h3 id=scope><span class=secno>1.1. </span>Scope</h3>
+  <h3 id=scope><span class=secno>1.1 </span>Scope</h3>
 
   <p>This specification is limited specifically to incremental improvements
    to existing wide-spread technologies, namely HTML4 and the DOM, as
@@ -512,7 +521,7 @@
   <p>Large sweeping changes or new markup languages are therefore out of
    scope for this specification.
 
-  <h3 id=r-to-html><span class=secno>1.2. </span>Relationship to HTML4</h3>
+  <h3 id=r-to-html><span class=secno>1.2 </span>Relationship to HTML4</h3>
 
   <p>This specification clarifies and extends the semantics put forth in <a
    href="#refsHTML4">[HTML4]</a> for form controls and form submission. It is
@@ -521,14 +530,14 @@
    have been implemented by user agents as ad-hoc, non-standard extensions
    for many years due to strong market demand.
 
-  <h3 id=r-to-xhtml><span class=secno>1.3. </span>Relationship to XHTML1.x</h3>
+  <h3 id=r-to-xhtml><span class=secno>1.3 </span>Relationship to XHTML1.x</h3>
 
   <p>This specification can also be viewed as an extension to <a
    href="#refsXHTML1">[XHTML1]</a>. In particular, some of the features added
    in this module only apply to XHTML documents; for example, features
    allowing mixed namespaces.
 
-  <h3 id=r-to-html5><span class=secno>1.4. </span>Relationship to HTML5</h3>
+  <h3 id=r-to-html5><span class=secno>1.4 </span>Relationship to HTML5</h3>
 
   <p>This specification is a prototype for what will become HTML5. It will
    eventually be merged with other proposals, such as those in the WHATWG Web
@@ -544,14 +553,14 @@
    HTML5 before addressing problems that arise from the current
    frankensteinesque style. <a href="#refsHTML5">[HTML5]</a>
 
-  <h3 id=r-to-dom><span class=secno>1.5. </span>Relationship to the W3C DOM</h3>
+  <h3 id=r-to-dom><span class=secno>1.5 </span>Relationship to the W3C DOM</h3>
 
   <p>This specification clarifies and extends the semantics put forth in <a
    href="#refsDOM2HTML">[DOM2HTML]</a> for the form control interfaces. These
    extensions are expected to be implemented in HTML and XHTML user agents
    that support the DOM.
 
-  <h3 id=r-to-xforms><span class=secno>1.6. </span>Relationship to XForms</h3>
+  <h3 id=r-to-xforms><span class=secno>1.6 </span>Relationship to XForms</h3>
 
   <p class=note>This section is aimed at XForms authors and implementors. If
    you do not plan to use XForms, you may prefer to skip ahead to the next
@@ -610,12 +619,12 @@
    syntax are, in this specification, handled by using scripting. Some new
    interfaces are introduced to simplify some of the more tedious tasks.
 
-  <h3 id=r-to-css><span class=secno>1.7. </span>Relationship to CSS</h3>
+  <h3 id=r-to-css><span class=secno>1.7 </span>Relationship to CSS</h3>
 
   <p>This specification does not extend CSS, but it does attempt to clarify
    some of the interactions between HTML's form features and CSS.
 
-  <h3 id=missing><span class=secno>1.8. </span>Missing features</h3>
+  <h3 id=missing><span class=secno>1.8 </span>Missing features</h3>
 
   <p>This draft does not address all needs. In addition to the features of
    XForms that have not been addressed (see above), the following features
@@ -651,7 +660,7 @@
     specification.
   </ul>
 
-  <h3 id=conformance><span class=secno>1.9. </span>Conformance requirements</h3>
+  <h3 id=conformance><span class=secno>1.9 </span>Conformance requirements</h3>
 
   <p>Conformance to this specification is defined for user agents (UAs,
    implementations) and documents (authors, authoring tools, markup
@@ -726,7 +735,7 @@
    specification cannot be strictly conforming XHTML1.1 or HTML4 documents,
    since they contain features not defined in those specifications.
 
-  <h3 id=terminology><span class=secno>1.10. </span>Terminology</h3>
+  <h3 id=terminology><span class=secno>1.10 </span>Terminology</h3>
 
   <p>This specification refers to both HTML and XML attributes and DOM
    attributes, often in the same context. When it is not clear which is being
@@ -756,7 +765,7 @@
    <code>http://n.whatwg.org/formdata</code> namespace.)
 
   <p>The term <dfn id=form-control>form control</dfn> refers to
-   <code>input</code>, <code><a href="#output0">output</a></code>,
+   <code>input</code>, <code><a href="#output">output</a></code>,
    <code>select</code>, <code>textarea</code> and <code>button</code>
    elements. It does not include <code>form</code>, <code>label</code>,
    <code><a href="#datalist">datalist</a></code>, <code>option</code>,
@@ -780,7 +789,7 @@
    section 5.18 "Case Mappings", subsection "Caseless Matching". <a
    href="#refsUNICODE">[UNICODE]</a>
 
-  <h3 id=extensibility><span class=secno>1.11. </span>Extensibility</h3>
+  <h3 id=extensibility><span class=secno>1.11 </span>Extensibility</h3>
 
   <p>Vendor-specific proprietary extensions to this specification are
    strongly discouraged. Documents must not use such extensions, as doing so
@@ -812,7 +821,7 @@
    processors), and styling them according to CSS (for CSS processors), but
    not inferring any meaning from them.
 
-  <h3 id=security><span class=secno>1.12. </span>Security</h3>
+  <h3 id=security><span class=secno>1.12 </span>Security</h3>
 
   <p>The delivery of Web Forms 2 documents to the user from a remote host and
    the submission of data from the user to a remote host may be performed
@@ -911,7 +920,7 @@
   <p>This section describes how Web Forms 2.0 expands the traditional HTML
    form model to support new types and features.
 
-  <h3 id=introduction0><span class=secno>2.1. </span>Introduction for authors</h3>
+  <h3 id=introduction0><span class=secno>2.1 </span>Introduction for authors</h3>
 
   <p><em>This subsection is not normative.</em>
 
@@ -971,7 +980,7 @@
                          <strong>oninvalid="alert('You must enter a valid home page address.'); return false;"</strong>>
 </label></pre>
 
-  <h3 id=existing><span class=secno>2.2. </span>Existing controls</h3>
+  <h3 id=existing><span class=secno>2.2 </span>Existing controls</h3>
 
   <p>HTML <code>input</code> elements use the <code>type</code> attribute to
    specify the data type. In <a href="#refsHTML4">[HTML4]</a>, the types (as
@@ -1063,7 +1072,7 @@
    to cover more specific data types, and introduces attributes that are
    designed to constrain data entry or other aspects of the UA's behaviour.
 
-  <h3 id=changes><span class=secno>2.3. </span>Changes to existing controls</h3>
+  <h3 id=changes><span class=secno>2.3 </span>Changes to existing controls</h3>
 
   <p><span id=emptyElements>In addition to the attributes described below,
    some changes are made to the content model of HTML form elements to take
@@ -1163,7 +1172,7 @@
    must submit the form as if there was an enabled, unnamed, default button.
    No <code>click</code> event is fired in this case.
 
-  <p class=note>Submit buttons can be <a href="#form0"
+  <p class=note>Submit buttons can be <a href="#form"
    title=form-attribute>associated with multiple forms</a>, but only ever
    submit to the first form they are associated with. A default button for
    one form, therefore, could submit a different form when implicitly invoked
@@ -1191,7 +1200,7 @@
    e.g. if an XML DTD is used, the XML specification can require certain
    attributes to have whitespace trimmed.
 
-  <h3 id=extensions><span class=secno>2.4. </span>Extensions to the
+  <h3 id=extensions><span class=secno>2.4 </span>Extensions to the
    <code>input</code> element</h3>
 
   <p>Several new values are introduced for the <code>type</code> attribute.
@@ -1524,7 +1533,7 @@
    <code>input</code> element is deprecated in favor of using CSS to specify
    the layout of the form.
 
-  <h4 id=ranges><span class=secno>2.4.1. </span>Ranges</h4>
+  <h4 id=ranges><span class=secno>2.4.1 </span>Ranges</h4>
 
   <p>To limit the range of values allowed by some of the above types, two new
    attributes are introduced, which apply to the date-related, time-related,
@@ -1605,7 +1614,7 @@
 <input type="time" min="22:00:50.0001"></pre>
   </div>
 
-  <h4 id=precision><span class=secno>2.4.2. </span>Precision</h4>
+  <h4 id=precision><span class=secno>2.4.2 </span>Precision</h4>
 
   <p>The <dfn id=step><code>step</code></dfn> attribute controls the
    precision allowed for the date-related, time-related, and numeric types.
@@ -1755,7 +1764,7 @@
    must be handled as described <a href="#errOORValue">in the error handling
    section</a>.
 
-  <h3 id=extensions0><span class=secno>2.5. </span>Extensions to existing
+  <h3 id=extensions0><span class=secno>2.5 </span>Extensions to existing
    attributes</h3>
 
   <p>In addition to the new attributes given in this section, some existing
@@ -1779,7 +1788,7 @@
 
    <dd>
     <p>The <code><a href="#disabled">disabled</a></code> attribute applies to
-     all form controls except the <code><a href="#output0">output</a></code>
+     all form controls except the <code><a href="#output">output</a></code>
      element, and also to the <code>fieldset</code>, <code>option</code>, and
      <code>optgroup</code> elements. <span class=note>In HTML4 the <code><a
      href="#disabled">disabled</a></code> attribute did not apply to the
@@ -1897,7 +1906,7 @@
   <p>Other attributes not listed in this specification retain the same
    semantics as in <a href="#refsHTML4">[HTML4]</a>.
 
-  <h3 id=the-pattern><span class=secno>2.6. </span>The <code><a
+  <h3 id=the-pattern><span class=secno>2.6 </span>The <code><a
    href="#pattern">pattern</a></code> attribute</h3>
 
   <p>For the <code><a href="#text">text</a></code>, <code><a
@@ -2033,7 +2042,7 @@
    be careful not to word <code>title</code>s as if an error has necessarily
    occurred.
 
-  <h3 id=the-required><span class=secno>2.7. </span>The <code id=required><a
+  <h3 id=the-required><span class=secno>2.7 </span>The <code id=required><a
    href="#required0">required</a></code> attribute</h3>
 
   <p>Form controls can have the <dfn id=required0><code>required</code></dfn>
@@ -2045,7 +2054,7 @@
    href="#hidden">hidden</a></code>, image inputs, buttons (<code><a
    href="#submit">submit</a></code>, <code><a
    href="#move-up">move-up</a></code>, etc), and <code>select</code> and
-   <code><a href="#output0">output</a></code> elements. For disabled or
+   <code><a href="#output">output</a></code> elements. For disabled or
    readonly controls, the attribute has no effect.
 
   <p id=satisfyingRequired>The <code><a
@@ -2084,7 +2093,7 @@
    href="#required0">required</a></code> condition, including a simple
    whitespace character.
 
-  <h3 id=formAttribute><span class=secno>2.8. </span>The <dfn id=form0
+  <h3 id=formAttribute><span class=secno>2.8 </span>The <dfn id=form
    title=form-attribute><code>form</code></dfn> attribute</h3>
 
   <p>All form controls as well as the <code>fieldset</code> element may have
@@ -2108,12 +2117,12 @@
 
   <p id=control-form-association>In other words, user agents must associated
    form controls and <code>fieldset</code>s with the forms given in their
-   <code title=form-attribute><a href="#form0">form</a></code> attribute, or,
+   <code title=form-attribute><a href="#form">form</a></code> attribute, or,
    if they don't have one, with the nearest ancestor <code>form</code>
    element or the forms given in the <code title=form-attribute><a
-   href="#form0">form</a></code> attribute of the nearest
+   href="#form">form</a></code> attribute of the nearest
    <code>fieldset</code> element with a <code title=form-attribute><a
-   href="#form0">form</a></code> attribute, whichever is the nearest. If none
+   href="#form">form</a></code> attribute, whichever is the nearest. If none
    of those apply, the element is not associated with any form.
 
   <p>When forms are submitted, are reset, or have their form controls
@@ -2202,7 +2211,7 @@
     the third button submits the same text control to <code>yahoo.cgi</code>.</p>
   </div>
 
-  <h3 id=the-autocomplete><span class=secno>2.9. </span>The <code><a
+  <h3 id=the-autocomplete><span class=secno>2.9 </span>The <code><a
    href="#autocomplete">autocomplete</a></code> attribute</h3>
 
   <p>The <dfn id=autocomplete><code>autocomplete</code></dfn> attribute
@@ -2258,12 +2267,12 @@
    implemented by most major Web browsers already, and has been for many
    years.
 
-  <h3 id=the-autofocus><span class=secno>2.10. </span>The <dfn
-   id=autofocus0><code>autofocus</code></dfn> attribute</h3>
+  <h3 id=the-autofocus><span class=secno>2.10 </span>The <dfn
+   id=autofocus><code>autofocus</code></dfn> attribute</h3>
 
   <p>Any form control (except <code><a href="#hidden">hidden</a></code> and
-   <code><a href="#output0">output</a></code> controls) can have an <code><a
-   href="#autofocus0">autofocus</a></code> attribute specified.
+   <code><a href="#output">output</a></code> controls) can have an <code><a
+   href="#autofocus">autofocus</a></code> attribute specified.
 
   <p>When a form control is inserted into a document, the UA must check to
    see if it has this attribute set. If it does, and the control is not <a
@@ -2273,14 +2282,13 @@
    viewport should also scroll the document enough to make the control
    visible, even if it is not of a type normally focusable.
 
-  <p>Authors must not set the <code><a
-   href="#autofocus0">autofocus</a></code> attribute on multiple enabled
-   elements in a document. If multiple elements with the <code><a
-   href="#autofocus0">autofocus</a></code> attribute set <em>are</em>
-   inserted into a document, each one will be processed as described above,
-   as they are inserted. This means that during document load, for example,
-   the last focusable form control in document order with the attribute set
-   will end up with the focus.
+  <p>Authors must not set the <code><a href="#autofocus">autofocus</a></code>
+   attribute on multiple enabled elements in a document. If multiple elements
+   with the <code><a href="#autofocus">autofocus</a></code> attribute set
+   <em>are</em> inserted into a document, each one will be processed as
+   described above, as they are inserted. This means that during document
+   load, for example, the last focusable form control in document order with
+   the attribute set will end up with the focus.
 
   <p>UAs may ignore this attribute if the user has indicated (for example, by
    starting to type in a form control) that he does not wish focus to be
@@ -2288,7 +2296,7 @@
 
   <p>The value of the attribute, if set, should be <code
    title="">autofocus</code>. The <code title=dom-autofocus><a
-   href="#autofocus1">autofocus</a></code> DOM attribute must return true
+   href="#autofocus0">autofocus</a></code> DOM attribute must return true
    when the content attribute is present (regardless of its value, even if it
    is the empty string), and false when it is absent. Setting the DOM
    attribute to true must set the content attribute to the value <code
@@ -2304,13 +2312,13 @@
   </div>
 
   <p>In HTML, the minimised form may be used (just <code><a
-   href="#autofocus0">autofocus</a></code> instead of
+   href="#autofocus">autofocus</a></code> instead of
    <code>autofocus="autofocus"</code>).
 
   <div class=example>
    <p>The following would cause the <code><a
-    href="#autofocus0">autofocus</a></code> attribute to be set to <code><a
-    href="#autofocus0">autofocus</a></code>:</p>
+    href="#autofocus">autofocus</a></code> attribute to be set to <code><a
+    href="#autofocus">autofocus</a></code>:</p>
 
    <pre><input autofocus></pre>
   </div>
@@ -2318,7 +2326,7 @@
   <p class=note>Focusing the control does not imply that the UA must focus
    the browser window if it has lost focus.
 
-  <h3 id=the-inputmode><span class=secno>2.11. </span>The <code><a
+  <h3 id=the-inputmode><span class=secno>2.11 </span>The <code><a
    href="#inputmode">inputmode</a></code> attribute</h3>
 
   <p>The <dfn id=inputmode><code>inputmode</code></dfn> attribute applies to
@@ -2335,7 +2343,7 @@
    specification</a> (sections E1 through E3.2) <a
    href="#refsXForms">[XForms]</a>.
 
-  <h3 id=the-datalist><span class=secno>2.12. </span>The <code><a
+  <h3 id=the-datalist><span class=secno>2.12 </span>The <code><a
    href="#datalist">datalist</a></code> element and the <code><a
    href="#list">list</a></code> attribute</h3>
 
@@ -2584,16 +2592,16 @@
    box, or any other widget or interface while still being compliant with
    this specification.
 
-  <h3 id=the-output><span class=secno>2.13. </span>The <dfn
-   id=output0><code>output</code></dfn> element</h3>
+  <h3 id=the-output><span class=secno>2.13 </span>The <dfn
+   id=output><code>output</code></dfn> element</h3>
 
-  <p>The <code><a href="#output0">output</a></code> element acts very much
+  <p>The <code><a href="#output">output</a></code> element acts very much
    like a <code>span</code> element, except that it is considered to be a
    form control for the purposes of the DOM. Its namespace (in XML) is the
    same as for the other form control elements,
    <code>http://www.w3.org/1999/xhtml</code>.
 
-  <p>The <code><a href="#output0">output</a></code> element may have any of
+  <p>The <code><a href="#output">output</a></code> element may have any of
    the <a href="http://www.w3.org/TR/html4/sgml/dtd.html#attrs">common
    attributes</a>, the <code>form</code> and <code><a
    href="#name">name</a></code> attributes, the <code><a
@@ -2611,7 +2619,7 @@
    href="#refsDOM3CORE">[DOM3CORE]</a>
 
   <p>The <em>initial value</em> of the <code><a
-   href="#output0">output</a></code> control is stored in a mutable <dfn
+   href="#output">output</a></code> control is stored in a mutable <dfn
    id=defaultvalue
    title=dom-output-defaultValue><code>defaultValue</code></dfn> DOM
    attribute of type <code>DOMString</code>. See <a
@@ -2622,8 +2630,8 @@
 
   <p id=outputDefaultValue>The <code title=dom-output-defaultValue><a
    href="#defaultvalue">defaultValue</a></code> DOM attribute of an <code><a
-   href="#output0">output</a></code> control must initially be set to the
-   empty string. If an <code><a href="#output0">output</a></code> element is
+   href="#output">output</a></code> control must initially be set to the
+   empty string. If an <code><a href="#output">output</a></code> element is
    added to the document at parse time, its <code
    title=dom-output-defaultValue><a
    href="#defaultvalue">defaultValue</a></code> DOM attribute must be set to
@@ -2636,10 +2644,10 @@
    href="#defaultvalue">defaultValue</a></code> must return the empty
    string.)
 
-  <p>The <code><a href="#output0">output</a></code> element is never <a
+  <p>The <code><a href="#output">output</a></code> element is never <a
    href="#successful">successful</a> for form submission. Resetting a form
-   <em>does</em> reset its <code><a href="#output0">output</a></code>
-   elements (using the <code title=dom-output-defaultValue><a
+   <em>does</em> reset its <code><a href="#output">output</a></code> elements
+   (using the <code title=dom-output-defaultValue><a
    href="#defaultvalue">defaultValue</a></code> DOM attribute — note
    that if the element originally contained elements as children, they will
    be removed when the form is reset).
@@ -2647,12 +2655,12 @@
   <p class=note>Unless the <code title=dom-output-value><a
    href="#value">value</a></code> attribute is directly manipulated or the
    form is reset, elements that are children of the <code><a
-   href="#output0">output</a></code> element when the document was parsed are
+   href="#output">output</a></code> element when the document was parsed are
    not flattened away.
 
   <div class=example>
    <p>The following example shows two input controls. Changing either control
-    updates an <code><a href="#output0">output</a></code> element containing
+    updates an <code><a href="#output">output</a></code> element containing
     the product of both controls.</p>
 
    <pre>
@@ -2686,16 +2694,16 @@
   <p>Authors may provide a list of space-separated IDs in a <dfn
    id=for><code>for</code></dfn> attribute that represents the list of
    elements that control the value of the <code><a
-   href="#output0">output</a></code> element. User agents may use this list
-   to suggest to users the relevant parts of the document with which the user
+   href="#output">output</a></code> element. User agents may use this list to
+   suggest to users the relevant parts of the document with which the user
    should interact to change the value.
 
   <div class=example>
-   <p>In the following example, the <code><a
-    href="#output0">output</a></code> element is used to indicate the
-    relationship between the given value and the later prose. The number
-    cannot be changed directly by the user, but the specified element
-    describes the process through which the user could change the value.</p>
+   <p>In the following example, the <code><a href="#output">output</a></code>
+    element is used to indicate the relationship between the given value and
+    the later prose. The number cannot be changed directly by the user, but
+    the specified element describes the process through which the user could
+    change the value.</p>
 
    <pre>
 ...
@@ -2709,17 +2717,17 @@
 
    <p>Note the <code>em</code> element in the markup emphasising a part of
     the number. Markup like this is allowed inside <code><a
-    href="#output0">output</a></code> elements.</p>
+    href="#output">output</a></code> elements.</p>
   </div>
 
   <p id=outputChange>Whenever the <code title=dom-output-value><a
    href="#value">value</a></code> attribute changes (whether directly or
    because the DOM under the element was mutated), a <code>change</code>
-   event must be fired on the <code><a href="#output0">output</a></code>
+   event must be fired on the <code><a href="#output">output</a></code>
    element. The <code>onchange</code> attribute can therefore be used with
    this element, in the same way as for other form controls.
 
-  <p><strong>Usage:</strong> The <code><a href="#output0">output</a></code>
+  <p><strong>Usage:</strong> The <code><a href="#output">output</a></code>
    element should be used when the user will never directly manipulate the
    value, and when the value can be derived from other values (e.g. a total),
    or, when the value is a repetition of a value editable elsewhere (e.g. a
@@ -2734,7 +2742,7 @@
    (controls that could be edited in some cases, for instance if the user had
    more privileges, but that are irrelevant at the current point in time).
 
-  <h3 id=extensions1><span class=secno>2.14. </span>Extensions to the
+  <h3 id=extensions1><span class=secno>2.14 </span>Extensions to the
    <code>textarea</code> element</h3>
 
   <p>The <code>rows</code> and <code>cols</code> attributes of the
@@ -2802,7 +2810,7 @@
    elements is separate from the <code><a href="#accept0">accept</a></code>
    attribute on file upload controls defined in the next section.
 
-  <h3 id=upload><span class=secno>2.15. </span>Extensions to file upload
+  <h3 id=upload><span class=secno>2.15 </span>Extensions to file upload
    controls</h3>
 
   <p>The <code><a href="#min">min</a></code> and <code><a
@@ -2927,7 +2935,7 @@
    create the submitted file on the fly) then the file name shall be the
    empty string for the purposes of submission.
 
-  <h3 id=extensions2><span class=secno>2.16. </span>Extensions to the
+  <h3 id=extensions2><span class=secno>2.16 </span>Extensions to the
    <code>form</code> element</h3>
 
   <p id=optionalAction>The <code>form</code> element's <code>action</code>
@@ -2976,7 +2984,7 @@
    href="#form-submission">the section on submission</a>, under <a
    href="#replaceSemantics">step eight</a>.
 
-  <h3 id=extensions3><span class=secno>2.17. </span>Extensions to the submit
+  <h3 id=extensions3><span class=secno>2.17 </span>Extensions to the submit
    buttons</h3>
 
   <p>Normally, activating a submit button (an <code>input</code> or
@@ -3003,7 +3011,7 @@
   <p>If the submit button is not associated with any form, then no form is
    submitted.
 
-  <h3 id=handling><span class=secno>2.18. </span>Handling unexpected elements
+  <h3 id=handling><span class=secno>2.18 </span>Handling unexpected elements
    and values</h3>
 
   <p>There are several elements that are defined as expecting particular
@@ -3052,7 +3060,7 @@
      href="#refsXBL2">[XBL2]</a>, however, it is possible for the author to
      override this behaviour.
 
-   <dt>For <code><a href="#output0">output</a></code> elements containing
+   <dt>For <code><a href="#output">output</a></code> elements containing
     elements in the DOM
 
    <dd>
@@ -3217,7 +3225,7 @@
    clients could be supported before user agents implemented it ubiquitously.
    Creating such a library is left as an exercise for the reader.
 
-  <h3 id=introduction1><span class=secno>3.1. </span>Introduction for authors</h3>
+  <h3 id=introduction1><span class=secno>3.1 </span>Introduction for authors</h3>
 
   <p><em>This subsection is not normative.</em>
 
@@ -3494,7 +3502,7 @@
   <p>Further examples are given in the <a href="#repeatExamples">examples
    section</a> below.
 
-  <h4 id=more-features><span class=secno>3.1.1. </span>More features</h4>
+  <h4 id=more-features><span class=secno>3.1.1 </span>More features</h4>
 
   <p>The repetition model supports more than just the cases given above; for
    instance, there are <code><a href="#move-up">move-up</a></code> and
@@ -3522,7 +3530,7 @@
   <p class=note>The naming schemes used above are arbitrary. Any naming
    scheme could be used, at the convenience of the author.
 
-  <h4 id=suggestions><span class=secno>3.1.2. </span>Suggestions for authors</h4>
+  <h4 id=suggestions><span class=secno>3.1.2 </span>Suggestions for authors</h4>
 
   <p>To include prefilled rows in the document, include copies of the row
    with <code><a href="#repeat">repeat</a></code> attributes having the value
@@ -3582,7 +3590,7 @@
    the controls as text fields. It is thus recommended that authors use
    <code>button</code> elements.
 
-  <h4 id=tracking><span class=secno>3.1.3. </span>Tracking the order of
+  <h4 id=tracking><span class=secno>3.1.3 </span>Tracking the order of
    repetition blocks in the submission</h4>
 
   <p>If a server-side framework does not preserve the order of fields
@@ -3592,14 +3600,14 @@
    repetition index. Then, to determine the order of the repetition blocks,
    the order of the values in this common control can be used.
 
-  <h4 id=what-the><span class=secno>3.1.4. </span>What the repetition model
+  <h4 id=what-the><span class=secno>3.1.4 </span>What the repetition model
    can't do</h4>
 
   <p>This specification does not address the ability to select a repetition
    block to move it up or down without using buttons directly associated with
    the current block.
 
-  <h4 id=small><span class=secno>3.1.5. </span>Small example for non-XHTML
+  <h4 id=small><span class=secno>3.1.5 </span>Small example for non-XHTML
    documents</h4>
 
   <p>This feature can also be used in non-XHTML documents. Here is an example
@@ -3614,7 +3622,7 @@
        <em>onclick="document.getElementById('blob').addRepetitionBlockByIndex(null, 1)"</em>/>
 </svg></pre>
 
-  <h3 id=definitions><span class=secno>3.2. </span>Definitions</h3>
+  <h3 id=definitions><span class=secno>3.2 </span>Definitions</h3>
 
   <p class=note>This section makes a number of references to namespaces. For
    authors who are only using HTML or XHTML, the definitions below ensure
@@ -3637,7 +3645,7 @@
    attribute. The effect of this attribute depends on its value, which can be
    either the literal string "<code title="">template</code>", or an integer.
 
-  <h4 id=repetition><span class=secno>3.2.1. </span>Repetition templates</h4>
+  <h4 id=repetition><span class=secno>3.2.1 </span>Repetition templates</h4>
 
   <p>An element in the <code>http://www.w3.org/1999/xhtml</code> namespace
    with the <span><code><a href="#repeat">repeat</a></code> attribute</span>
@@ -3670,7 +3678,7 @@
    these descriptions to help users. (Note, though, that such titles would
    get propagated to the repetition blocks too.)
 
-  <h4 id=repetition0><span class=secno>3.2.2. </span>Repetition blocks</h4>
+  <h4 id=repetition0><span class=secno>3.2.2 </span>Repetition blocks</h4>
 
   <p>An element in the <code>http://www.w3.org/1999/xhtml</code> namespace
    with the <span><code><a href="#repeat">repeat</a></code> attribute</span>
@@ -3735,7 +3743,7 @@
 <div repeat="0"/> <!-- Orphan repetition block, index 0. -->
 </pre>
 
-  <h3 id=new-form><span class=secno>3.3. </span>New form controls</h3>
+  <h3 id=new-form><span class=secno>3.3 </span>New form controls</h3>
 
   <p>Several new button types are introduced to support the repetition model.
    These values are valid types for both the <code>button</code> element and
@@ -3792,7 +3800,7 @@
   <p>These new types and attributes are described in more detail in the next
    few sections.
 
-  <h3 id=the-repeat-min><span class=secno>3.4. </span>The <code><a
+  <h3 id=the-repeat-min><span class=secno>3.4 </span>The <code><a
    href="#repeat-min">repeat-min</a></code> and <code><a
    href="#repeat-max">repeat-max</a></code> attributes</h3>
 
@@ -3830,7 +3838,7 @@
    allow a form to be <a href="#data0" title=form-data>seeded with initial
    values from an external file</a>.
 
-  <h3 id=event><span class=secno>3.5. </span>Event interface for repetition
+  <h3 id=event><span class=secno>3.5 </span>Event interface for repetition
    events</h3>
 
   <p>The repetition model includes several events. The <code><a
@@ -3869,7 +3877,7 @@
    id=element title=dom-RepetitionEvent-element><code>element</code></dfn>
    attribute.
 
-  <h3 id=repetitionModel><span class=secno>3.6. </span>The repetition model</h3>
+  <h3 id=repetitionModel><span class=secno>3.6 </span>The repetition model</h3>
 
   <p>A <a href="#repetition2">repetition template</a> should not be
    displayed. In CSS-aware user agents, this should be achieved by including
@@ -3894,7 +3902,7 @@
    title=form-data>seeding a form with initial values</a> for details on how
    repetition blocks can be prefilled.
 
-  <h4 id=addition><span class=secno>3.6.1. </span>Addition</h4>
+  <h4 id=addition><span class=secno>3.6.1 </span>Addition</h4>
 
   <p>If an <code><a href="#add">add</a></code> button with a <code><a
    href="#template">template</a></code> attribute is activated, and its
@@ -4081,7 +4089,7 @@
   <p>For an example, see the <a href="#repeatExample">example section</a>
    below.
 
-  <h4 id=removal><span class=secno>3.6.2. </span>Removal</h4>
+  <h4 id=removal><span class=secno>3.6.2 </span>Removal</h4>
 
   <p>If a <code><a href="#remove">remove</a></code> button is activated, and
    the element has an ancestor that is a <a href="#repetition3">repetition
@@ -4130,7 +4138,7 @@
   <p>For an example, see the <a href="#repeatExample">example section</a>
    below.
 
-  <h4 id=movement><span class=secno>3.6.3. </span>Movement of repetition
+  <h4 id=movement><span class=secno>3.6.3 </span>Movement of repetition
    blocks</h4>
 
   <p>The two remaining button types, <code><a
@@ -4210,7 +4218,7 @@
    not affect the DOM <code><a href="#disabled">disabled</a></code>
    attribute. It is an intrinsic property of these buttons.
 
-  <h4 id=initial><span class=secno>3.6.4. </span>Initial repetition blocks</h4>
+  <h4 id=initial><span class=secno>3.6.4 </span>Initial repetition blocks</h4>
 
   <p>The <dfn id=repeat-start><code>repeat-start</code></dfn> attribute on
    repetition templates is used to insert repetition blocks at load time
@@ -4254,7 +4262,7 @@
   <p>UAs should not specifically wait for images and style sheets to be
    loaded before creating initial repetition blocks as described above.
 
-  <h4 id=notes><span class=secno>3.6.5. </span>Notes for assistive
+  <h4 id=notes><span class=secno>3.6.5 </span>Notes for assistive
    technologies</h4>
 
   <p>The repetition templates and blocks are present in the DOM, and all
@@ -4263,11 +4271,11 @@
    Assistive technologies can therefore use normal DOM navigation and
    mutation event listeners to help present repetition sections to the user.
 
-  <h3 id=repeatExamples><span class=secno>3.7. </span>Examples</h3>
+  <h3 id=repeatExamples><span class=secno>3.7 </span>Examples</h3>
 
   <p>This section gives some more practical examples of repetition.
 
-  <h4 id=repeatExample><span class=secno>3.7.1. </span>Repeated rows</h4>
+  <h4 id=repeatExample><span class=secno>3.7.1 </span>Repeated rows</h4>
 
   <p>The following example shows how to use repetition templates to
    dynamically add rows to a form in a table.
@@ -4324,7 +4332,7 @@
 
   <p>If the "Delete Row" button above is pressed, the row is removed.
 
-  <h4 id=nested><span class=secno>3.7.2. </span>Nested repeats</h4>
+  <h4 id=nested><span class=secno>3.7.2 </span>Nested repeats</h4>
 
   <p>The previous example does not demonstrate nested repeat blocks,
    reordering repetition blocks, and inserting new repetition blocks in the
@@ -4413,7 +4421,7 @@
   <p class=note>The repetition model events are not form events since they
    are not form-specific.
 
-  <h3 id=the-click><span class=secno>4.1. </span>The <code>click</code> event
+  <h3 id=the-click><span class=secno>4.1 </span>The <code>click</code> event
    and <code>input</code> controls</h3>
 
   <p>During the handling of a <code>click</code> event on an
@@ -4436,7 +4444,7 @@
    href="http://www.w3.org/TR/DOM-Level-2-HTML/html.html#ID-30233917">this
    behaviour was optional</a>. <a href="#refsDOM2HTML">[DOM2HTML]</a>
 
-  <h3 id=the-change><span class=secno>4.2. </span>The <code>change</code> and
+  <h3 id=the-change><span class=secno>4.2 </span>The <code>change</code> and
    <code>input</code> events</h3>
 
   <p>In <a href="#refsDOM3EVENTS">[DOM3EVENTS]</a> and <a
@@ -4481,16 +4489,16 @@
 
   <p>Change and input events must never be triggered by scripted changes to
    the control value (except <a href="#outputChange">in the case of</a> the
-   <code><a href="#output0">output</a></code> element). Thus, loops caused by
+   <code><a href="#output">output</a></code> element). Thus, loops caused by
    change event handlers triggering changes are not usually possible.
 
   <p>Any element that accepts an <code>onchange</code> attribute to handle
    <code>change</code> events shall also accept an <code>oninput</code>
    attribute to handle <code>input</code> events, except the <code><a
-   href="#output0">output</a></code> element (for which it would make no
+   href="#output">output</a></code> element (for which it would make no
    sense).
 
-  <h3 id=events><span class=secno>4.3. </span>Events to enable simpler
+  <h3 id=events><span class=secno>4.3 </span>Events to enable simpler
    dependency tracking</h3>
 
   <p>Sometimes form controls are inter-dependent. In these cases, it is more
@@ -4513,16 +4521,16 @@
    controls, they should hook into the form's <code>onformchange</code> event
    handler.
 
-  <p>The exception is the <code><a href="#output0">output</a></code> control.
-   Since changing an <code><a href="#output0">output</a></code> control is
+  <p>The exception is the <code><a href="#output">output</a></code> control.
+   Since changing an <code><a href="#output">output</a></code> control is
    often the result of a <code><a href="#formchange">formchange</a></code>
    event, <code>change</code> events whose target is an <code><a
-   href="#output0">output</a></code> control do not cause <code><a
+   href="#output">output</a></code> control do not cause <code><a
    href="#formchange">formchange</a></code> events to be dispatched.
 
   <p>The <code>input</code> event analogously invokes the <code><a
    href="#forminput">forminput</a></code> event as its default action (again,
-   except if the target is an <code><a href="#output0">output</a></code>
+   except if the target is an <code><a href="#output">output</a></code>
    control).
 
   <p>When a form is reset, a <code><a
@@ -4540,7 +4548,7 @@
    which <a href="#seeding">is equivalent to seeding a form with no new
    values</a>.
 
-  <h3 id=form-validation><span class=secno>4.4. </span>Form validation</h3>
+  <h3 id=form-validation><span class=secno>4.4 </span>Form validation</h3>
 
   <p>With the introduction of the various type-checking mechanisms, some way
    for scripting authors to hook into the type-checking process is required.
@@ -4678,8 +4686,8 @@
 </pre>
   </div>
 
-  <h3 id=receiving><span class=secno>4.5. </span>Receiving the results of
-   form submission</h3>
+  <h3 id=receiving><span class=secno>4.5 </span>Receiving the results of form
+   submission</h3>
 
   <p>The <dfn id=receivedevent><code>ReceivedEvent</code></dfn> interface is
    used in the form submission process to handle the results of form
@@ -4711,7 +4719,7 @@
    was the result of the form submission. If the result cannot be represented
    as a DOM document, then the attribute is null. The document is mutable.
 
-  <h3 id=the-domcontrolvaluechanged><span class=secno>4.6. </span>The
+  <h3 id=the-domcontrolvaluechanged><span class=secno>4.6 </span>The
    <code>DOMControlValueChanged</code> event</h3>
 
   <p>A <code>DOMControlValueChanged</code> event, which bubbles, is not
@@ -4798,7 +4806,7 @@
      name was associated with an earlier control, then the index assigned is
      exactly one more than the last control with that name. Even unsuccessful
      controls and controls with <a href="#no-value">no value selected</a> are
-     so numbered (including <code><a href="#output0">output</a></code>
+     so numbered (including <code><a href="#output">output</a></code>
      elements). However, only <a href="#successful">successful controls</a>
      are added to the form data set.</p>
 
@@ -4944,7 +4952,7 @@
      <code>form</code>, then the relevant attribute on the element's
      associated <code>form</code> element is used instead. (If it is
      associated with multiple forms, the first one in the order given in the
-     <code title=form-attribute><a href="#form0">form</a></code> attribute is
+     <code title=form-attribute><a href="#form">form</a></code> attribute is
      used.) The <a href="#methodAndEnctypes"><!--semantics
     of <code>method</code> and <code>enctype</code> attributes:
     -->submitting
@@ -5028,7 +5036,7 @@
   <p>If the submission process fails, UAs should report this failure to the
    user in a useful and accessible manner.
 
-  <h3 id=successful><span class=secno>5.1. </span>Successful form controls</h3>
+  <h3 id=successful><span class=secno>5.1 </span>Successful form controls</h3>
 
   <p>The controls that are <dfn id=successful0>successful</dfn> are those
    that are included in the submission (in the form data set) when their form
@@ -5071,7 +5079,7 @@
 
   <p>Controls do not have to have a value to be successful.
 
-  <h3 id=unacceptableCharacters><span class=secno>5.2. </span>Handling
+  <h3 id=unacceptableCharacters><span class=secno>5.2 </span>Handling
    characters outside the submission character encoding</h3>
 
   <p>The different form data set encoding types each define how to find the
@@ -5126,18 +5134,18 @@
    there is no way to distinguish such characters from identical literal
    strings entered by the user.)
 
-  <h4 id=the-charset><span class=secno>5.2.1. </span>The <dfn
-   id=charset0><code>_charset_</code></dfn> control</h4>
+  <h4 id=the-charset><span class=secno>5.2.1 </span>The <dfn
+   id=charset><code>_charset_</code></dfn> control</h4>
 
   <p>The <code>application/x-www-form-urlencoded</code> and
    <code>text/plain</code> encoding types for the form data set look for a
    <code><a href="#hidden">hidden</a></code> form control with the name
-   <code><a href="#charset0">_charset_</a></code>, and if it is present in
-   the form data set, they include it in the submission with the submission
+   <code><a href="#charset">_charset_</a></code>, and if it is present in the
+   form data set, they include it in the submission with the submission
    encoding. This allows authors to determine the encoding that was used in
    submissions that would otherwise be ambiguous.
 
-  <h3 id=x-www-form-urlencoded><span class=secno>5.3.
+  <h3 id=x-www-form-urlencoded><span class=secno>5.3
    </span><code>application/x-www-form-urlencoded</code></h3>
 
   <p>This section defines the expected behaviour for step 5, "Step five:
@@ -5173,7 +5181,7 @@
 
    <li>If the form contains an input control of type <code><a
     href="#hidden">hidden</a></code> with the name <code><a
-    href="#charset0">_charset_</a></code>, it is forced to appear in the form
+    href="#charset">_charset_</a></code>, it is forced to appear in the form
     data set, with the value equal to the name of the submission character
     encoding used.
 
@@ -5195,7 +5203,7 @@
   <p> Note that the control index and repetition block parts of the form data
    set are not used.
 
-  <h3 id=x-www-form-xml><span class=secno>5.4.
+  <h3 id=x-www-form-xml><span class=secno>5.4
    </span><code>application/x-www-form+xml</code>: XML submission</h3>
 
   <p>This section defines the expected behaviour for step 5, "Step five:
@@ -5407,7 +5415,7 @@
   its context information. this could be passed to an XSLT processor
   to turn the submission XML into a new format.]</p> -->
 
-  <h3 id=text-plain><span class=secno>5.5. </span><code>text/plain</code></h3>
+  <h3 id=text-plain><span class=secno>5.5 </span><code>text/plain</code></h3>
 
   <p>This section defines the expected behaviour for step 5, "Step five:
    Encode the form data set", of the submission algorithm described above,
@@ -5437,7 +5445,7 @@
 
    <li>If the form contains an input control of type <code><a
     href="#hidden">hidden</a></code> with the name <code><a
-    href="#charset0">_charset_</a></code>, it is forced to appear in the form
+    href="#charset">_charset_</a></code>, it is forced to appear in the form
     data set, with the value equal to the name of the submission character
     encoding used.
 
@@ -5457,7 +5465,7 @@
    <code>application/x-www-form-urlencoded</code>. This is mostly due to
    backwards compatibility concerns (for both cases).
 
-  <h3 id=methodAndEnctypes><span class=secno>5.6.
+  <h3 id=methodAndEnctypes><span class=secno>5.6
    </span><!--Semantics of <code>method</code> and
   <code>enctype</code> attributes: -->Submitting
    the encoded form data set</h3>
@@ -5537,7 +5545,7 @@
    otherwise meaningless. In such cases, the encoded data set is created from
    the fallback encoding type, not the specified encoding type.
 
-  <h4 id=for-http><span class=secno>5.6.1. </span>For <code>http:</code>
+  <h4 id=for-http><span class=secno>5.6.1 </span>For <code>http:</code>
    actions</h4>
 
   <p>HTTP is described by <a href="#refsRFC2616">[RFC2616]</a>.
@@ -5596,8 +5604,7 @@
    data set was <code>foo=bar</code> then the resulting URI would be
    <code>http://example.com/?foo=bar</code>.
 
-  <h4 id=for-ftp><span class=secno>5.6.2. </span>For <code>ftp:</code>
-   actions</h4>
+  <h4 id=for-ftp><span class=secno>5.6.2 </span>For <code>ftp:</code> actions</h4>
 
   <p>The <code>ftp:</code> URI scheme is described by <a
    href="#refsRFC1738">[RFC1738]</a> and FTP itself is described by <a
@@ -5677,7 +5684,7 @@
   </div>
 -->
 
-  <h4 id=for-data><span class=secno>5.6.3. </span>For <code>data:</code>
+  <h4 id=for-data><span class=secno>5.6.3 </span>For <code>data:</code>
    actions</h4>
 
   <p>The <code>data:</code> URI scheme is described by <a
@@ -5760,7 +5767,7 @@
   <p><strong>Usage:</strong> Submitting to data: URIs is mainly useful when
    debugging (to find out exactly what is being submitted).
 
-  <h4 id=for-file><span class=secno>5.6.4. </span>For <code><a
+  <h4 id=for-file><span class=secno>5.6.4 </span>For <code><a
    href="#file">file:</a></code> actions</h4>
 
   <p><em>This section is not normative.</em>
@@ -5882,7 +5889,7 @@
    submission format and preseeding, as it allows data to be stored locally
    between uses of the application.
 
-  <h4 id=for-mailto><span class=secno>5.6.5. </span>For <code>mailto:</code>
+  <h4 id=for-mailto><span class=secno>5.6.5 </span>For <code>mailto:</code>
    actions</h4>
 
   <p>The <code>mailto:</code> URI scheme is described by <a
@@ -5941,7 +5948,7 @@
       <code>action</code> attribute.
   </table>
 
-  <h4 id=for-javascript><span class=secno>5.6.6. </span>For
+  <h4 id=for-javascript><span class=secno>5.6.6 </span>For
    <code>javascript:</code> actions</h4>
 
   <p>The <code>javascript:</code> URI scheme is <a
@@ -6073,7 +6080,7 @@
    Similarly, cross-domain scripting restrictions are fully expected to
    apply.
 
-  <h3 id=selectSeeding><span class=secno>6.1. </span>Filling
+  <h3 id=selectSeeding><span class=secno>6.1 </span>Filling
    <code>select</code> elements</h3>
 
   <p>If a <code>select</code> element or a <code><a
@@ -6154,7 +6161,7 @@
     which, in due course, will have two options, namely "a" and "b".</p>
   </div>
 
-  <h3 id=seeding><span class=secno>6.2. </span>Seeding a form with initial
+  <h3 id=seeding><span class=secno>6.2 </span>Seeding a form with initial
    values</h3>
 
   <p>Before <code>load</code> events are fired, but after the entire document
@@ -6345,10 +6352,10 @@
    implies that this process cannot be performed incrementally.)
 
   <p class=note>Note that file upload controls cannot be repopulated.
-   However, an <code><a href="#output0">output</a></code> control
-   <em>can</em> be populated. This can be used, for example, for localizing a
-   form by including the structure in one file and the strings in another.
-   (The semantics of this practice are somewhat dubious, however. It is only
+   However, an <code><a href="#output">output</a></code> control <em>can</em>
+   be populated. This can be used, for example, for localizing a form by
+   including the structure in one file and the strings in another. (The
+   semantics of this practice are somewhat dubious, however. It is only
    mentioned because XForms advocates claim this as a feature.)</p>
   <!--
    Take:
@@ -6432,7 +6439,7 @@
            attribute unsigned long   <code title="">length</code>;
                                         // raises(DOMException) on setting
 
-  readonly attribute HTMLFormElement <code title=dom-form><a href="#form1">form</a></code>;
+  readonly attribute HTMLFormElement <code title=dom-form><a href="#form0">form</a></code>;
   readonly attribute HTMLOptionsCollection <code title="">options</code>;
            attribute boolean         <code title=dom-disabled><a href="#disabled1">disabled</a></code>;
            attribute boolean         <code title="">multiple</code>;
@@ -6449,7 +6456,7 @@
   // new in this specification:
   readonly attribute NodeList        <code><a href="#forms">forms</a></code>;
            attribute DOMString       <code title=dom-accessKey>accessKey</code>;
-           attribute boolean         <code title=dom-autofocus><a href="#autofocus1">autofocus</a></code>;
+           attribute boolean         <code title=dom-autofocus><a href="#autofocus0">autofocus</a></code>;
            attribute DOMString       <code title=dom-data><a href="#data1">data</a></code>;
   readonly attribute HTMLCollection  <code title=dom-selectedOptions><a href="#selectedoptions">selectedOptions</a></code>;
   readonly attribute HTMLCollection  <code title=dom-labels><a href="#labels0">labels</a></code>;
@@ -6474,7 +6481,7 @@
 };
 
 interface <dfn id=htmloptionelement>HTMLOptionElement</dfn> : <code>HTMLElement</code> {
-  readonly attribute HTMLFormElement <code title=dom-form><a href="#form1">form</a></code>;
+  readonly attribute HTMLFormElement <code title=dom-form><a href="#form0">form</a></code>;
            attribute boolean         <code title=dom-defaultSelected>defaultSelected</code>;
   readonly attribute DOMString       <code title=dom-text>text</code>;
   readonly attribute long            <code title=dom-index>index</code>;
@@ -6490,7 +6497,7 @@
 interface <dfn id=htmlinputelement>HTMLInputElement</dfn> : <code>HTMLElement</code> {
            attribute DOMString       <code title=dom-input-defaultValue><a href="#defaultvalue0">defaultValue</a></code>;
            attribute boolean         <code title=dom-defaultChecked>defaultChecked</code>;
-  readonly attribute HTMLFormElement <code title=dom-form><a href="#form1">form</a></code>;
+  readonly attribute HTMLFormElement <code title=dom-form><a href="#form0">form</a></code>;
            attribute DOMString       <code title=dom-accept><a href="#accept2">accept</a></code>;
            attribute DOMString       <code title=dom-accessKey>accessKey</code>;
            attribute DOMString       <code title=dom-align>align</code>;
@@ -6519,7 +6526,7 @@
            attribute DOMString       <code title=dom-pattern><a href="#pattern0">pattern</a></code>;
            attribute boolean         <code title=dom-required><a href="#required1">required</a></code>;
            attribute boolean         <code title=dom-autocomplete><a href="#autocomplete0">autocomplete</a></code>;
-           attribute boolean         <code title=dom-autofocus><a href="#autofocus1">autofocus</a></code>;
+           attribute boolean         <code title=dom-autofocus><a href="#autofocus0">autofocus</a></code>;
            attribute DOMString       <code title=dom-inputmode><a href="#inputmode0">inputmode</a></code>;
            attribute DOMString       <code title=dom-action><a href="#action">action</a></code>;
            attribute DOMString       <code title=dom-enctype><a href="#enctype">enctype</a></code>;
@@ -6552,7 +6559,7 @@
 
 interface <dfn id=htmltextareaelement>HTMLTextAreaElement</dfn> : <code>HTMLElement</code> {
            attribute DOMString       <code title=dom-textarea-defaultValue><a href="#defaultvalue1">defaultValue</a></code>;
-  readonly attribute HTMLFormElement <code title=dom-form><a href="#form1">form</a></code>;
+  readonly attribute HTMLFormElement <code title=dom-form><a href="#form0">form</a></code>;
            attribute DOMString       <code title=dom-accessKey>accessKey</code>;
            attribute long            <code title=dom-cols>cols</code>;
            attribute boolean         <code title=dom-disabled><a href="#disabled1">disabled</a></code>;
@@ -6571,7 +6578,7 @@
            attribute DOMString       <code title=dom-wrap><a href="#wrap0">wrap</a></code>;
            attribute DOMString       <code title=dom-pattern><a href="#pattern0">pattern</a></code>;
            attribute boolean         <code title=dom-required><a href="#required1">required</a></code>;
-           attribute boolean         <code title=dom-autofocus><a href="#autofocus1">autofocus</a></code>;
+           attribute boolean         <code title=dom-autofocus><a href="#autofocus0">autofocus</a></code>;
            attribute DOMString       <code title=dom-inputmode><a href="#inputmode0">inputmode</a></code>;
            attribute long            <code title=dom-maxLength>maxLength</code>;
            attribute DOMString       <code title=dom-accept><a href="#accept2">accept</a></code>;
@@ -6591,7 +6598,7 @@
 };
 
 interface <dfn id=htmlbuttonelement>HTMLButtonElement</dfn> : <code>HTMLElement</code> {
-  readonly attribute HTMLFormElement <code title=dom-form><a href="#form1">form</a></code>;
+  readonly attribute HTMLFormElement <code title=dom-form><a href="#form0">form</a></code>;
            attribute DOMString       <code title=dom-accessKey>accessKey</code>;
            attribute boolean         <code title=dom-disabled><a href="#disabled1">disabled</a></code>;
            attribute DOMString       <code title=dom-name>name</code>;
@@ -6608,7 +6615,7 @@
            attribute DOMString       <code title=dom-method><a href="#method">method</a></code>;
            attribute DOMString       <code title=dom-target><a href="#target">target</a></code>;
            attribute DOMString       <code title=dom-replace><a href="#replace0">replace</a></code>;
-           attribute boolean         <code title=dom-autofocus><a href="#autofocus1">autofocus</a></code>;
+           attribute boolean         <code title=dom-autofocus><a href="#autofocus0">autofocus</a></code>;
   readonly attribute HTMLCollection  <code title=dom-labels><a href="#labels0">labels</a></code>;
   readonly attribute <code><a href="#repetitionelement0">RepetitionElement</a></code> <code title=dom-htmlTemplate><a href="#htmltemplate">htmlTemplate</a></code>;
   void               <code title=blur>blur</code>();
@@ -6624,7 +6631,7 @@
 };
 
 interface <dfn id=htmllabelelement>HTMLLabelElement</dfn> : <code>HTMLElement</code> {
-  readonly attribute HTMLFormElement <code title=dom-form><a href="#form1">form</a></code>;
+  readonly attribute HTMLFormElement <code title=dom-form><a href="#form0">form</a></code>;
            attribute DOMString       <code title=dom-accessKey>accessKey</code>;
            attribute DOMString       <code title=dom-htmlFor>htmlFor</code>;
 
@@ -6634,7 +6641,7 @@
 };
 
 interface <dfn id=htmlfieldsetelement>HTMLFieldSetElement</dfn> : <code>HTMLElement</code> {
-  readonly attribute HTMLFormElement <code title=dom-form><a href="#form1">form</a></code>;
+  readonly attribute HTMLFormElement <code title=dom-form><a href="#form0">form</a></code>;
 
   // new in this specification
   readonly attribute NodeList        <code><a href="#forms">forms</a></code>;
@@ -6649,7 +6656,7 @@
 };
 
 interface <dfn id=htmllegendelement>HTMLLegendElement</dfn> : <code>HTMLElement</code> {
-  readonly attribute HTMLFormElement <code title=dom-form><a href="#form1">form</a></code>;
+  readonly attribute HTMLFormElement <code title=dom-form><a href="#form0">form</a></code>;
            attribute DOMString       <code title=dom-accessKey>accessKey</code>;
            attribute DOMString       <code title=dom-align>align</code>;
 
@@ -6660,7 +6667,7 @@
 // new in this specification
 interface <dfn id=htmloutputelement>HTMLOutputElement</dfn> : HTMLElement {
            attribute DOMString       <code title=dom-output-defaultValue><a href="#defaultvalue">defaultValue</a></code>;
-  readonly attribute HTMLFormElement <code title=dom-form><a href="#form1">form</a></code>;
+  readonly attribute HTMLFormElement <code title=dom-form><a href="#form0">form</a></code>;
   readonly attribute NodeList        <code><a href="#forms">forms</a></code>;
            attribute DOMString       <code title=dom-name>name</code>;
            attribute DOMString       <code title=dom-output-value><a href="#value">value</a></code>;
@@ -6705,7 +6712,7 @@
 };
 </pre>
 
-  <h3 id=additions><span class=secno>7.1. </span>Additions specific to the
+  <h3 id=additions><span class=secno>7.1 </span>Additions specific to the
    <code><a href="#htmlformelement">HTMLFormElement</a></code> interface</h3>
 
   <p>The new <dfn id=accept1 title=dom-accept><code>accept</code></dfn>
@@ -6714,7 +6721,7 @@
    addresses an oversight in DOM2.
 
   <p>The <dfn id=elements><code>elements</code></dfn> array must contain all
-   the <code>input</code>, <code><a href="#output0">output</a></code>,
+   the <code>input</code>, <code><a href="#output">output</a></code>,
    <code>select</code>, <code>textarea</code>, <code>button</code>, and
    <code>fieldset</code> elements that are <a
    href="#control-form-association">associated with the form</a> except those
@@ -6786,7 +6793,7 @@
   <p>If a name is used by exactly one control, the form object has a property
    of that name that references that control.
 
-  <h3 id=additions0><span class=secno>7.2. </span>Additions specific to the
+  <h3 id=additions0><span class=secno>7.2 </span>Additions specific to the
    <code><a href="#htmlselectelement">HTMLSelectElement</a></code> interface</h3>
 
   <p>The <dfn id=selectedoptions
@@ -6829,7 +6836,7 @@
   compatibility with existing content.</p>
 -->
 
-  <h3 id=the-htmldatalistelement><span class=secno>7.3. </span>The <code><a
+  <h3 id=the-htmldatalistelement><span class=secno>7.3 </span>The <code><a
    href="#htmldatalistelement">HTMLDataListElement</a></code> interface</h3>
 
   <p>The <code>options</code> element returns the same as
@@ -6838,7 +6845,7 @@
    namespaced version was called with the same tag name but with the XHTML
    namespace).
 
-  <h3 id=changes0><span class=secno>7.4. </span>Changes to the <code><a
+  <h3 id=changes0><span class=secno>7.4 </span>Changes to the <code><a
    href="#htmloptionelement">HTMLOptionElement</a></code> interface</h3>
 
   <p>The <dfn id=index title=HTMLOptionElement.index><code>index</code></dfn>
@@ -6855,7 +6862,7 @@
    an ambiguity in DOM2 HTML's definition of the attribute: it was undefined
    if the parent was not a <code>select</code> element.
 
-  <h3 id=additions1><span class=secno>7.5. </span>Additions specific to the
+  <h3 id=additions1><span class=secno>7.5 </span>Additions specific to the
    <code><a href="#htmlfieldsetelement">HTMLFieldsetElement</a></code>
    interface</h3>
 
@@ -6863,23 +6870,23 @@
    title=dom-fieldset-elements><code>elements</code></dfn> attribute lists
    the form controls under the <code>fieldset</code>, regardless of which
    form they belong to. The array must contain all the <code>input</code>,
-   <code><a href="#output0">output</a></code>, <code>select</code>,
+   <code><a href="#output">output</a></code>, <code>select</code>,
    <code>textarea</code> and <code>button</code> controls that have the
    <code>fieldset</code> element as an ancestor, in document order.
 
-  <h3 id=the-htmloutputelement><span class=secno>7.6. </span>The <code><a
+  <h3 id=the-htmloutputelement><span class=secno>7.6 </span>The <code><a
    href="#htmloutputelement">HTMLOutputElement</a></code> interface</h3>
 
   <p>This interface is added for the new <code><a
-   href="#output0">output</a></code> element. Its attributes work analogously
+   href="#output">output</a></code> element. Its attributes work analogously
    to those on other controls. The semantics of the <code
    title=dom-output-value><a href="#value">value</a></code> and <code
    title=dom-output-defaultValue><a
    href="#defaultvalue">defaultValue</a></code> DOM attributes are described
-   in the section describing the <code><a href="#output0">output</a></code>
+   in the section describing the <code><a href="#output">output</a></code>
    element.
 
-  <h3 id=validation><span class=secno>7.7. </span>Validation APIs</h3>
+  <h3 id=validation><span class=secno>7.7 </span>Validation APIs</h3>
 
   <p>The <dfn id=willvalidate><code>willValidate</code></dfn> attribute of a
    form control element must return true if all of the following conditions
@@ -6906,7 +6913,7 @@
     <code><a href="#move-up">move-up</a></code>, or <code><a
     href="#move-down">move-down</a></code>.
 
-   <li>The control is not an <code><a href="#output0">output</a></code>
+   <li>The control is not an <code><a href="#output">output</a></code>
     element.
   </ul>
 
@@ -7065,17 +7072,17 @@
    interfaces implement these attributes and methods so that when iterating
    over the form's <code><a href="#elements">elements</a></code> array,
    authors do not have to ensure that each form element is not an <code><a
-   href="#output0">output</a></code> element or a <code>button</code> before
+   href="#output">output</a></code> element or a <code>button</code> before
    using them.
 
-  <h3 id=new-dom><span class=secno>7.8. </span>New DOM attributes for new
+  <h3 id=new-dom><span class=secno>7.8 </span>New DOM attributes for new
    content attributes</h3>
 
   <p>The new <dfn id=data1 title=dom-data><code>data</code></dfn>, <dfn
    id=pattern0 title=dom-pattern><code>pattern</code></dfn>, <dfn
    id=required1 title=dom-required><code>required</code></dfn>, <dfn
    id=autocomplete0 title=dom-autocomplete><code>autocomplete</code></dfn>,
-   <dfn id=autofocus1 title=dom-autofocus><code>autofocus</code></dfn>, <dfn
+   <dfn id=autofocus0 title=dom-autofocus><code>autofocus</code></dfn>, <dfn
    id=inputmode0 title=dom-inputmode><code>inputmode</code></dfn>, <dfn
    id=min0 title=dom-min><code>min</code></dfn>, <dfn id=max0
    title=dom-max><code>max</code></dfn>, <dfn id=step0
@@ -7108,24 +7115,24 @@
    control interfaces is a live read-only <code>NodeList</code>, which shall
    contain the forms that the control is associated with, as determined by,
    and in the order given by, the <code title=form-attribute><a
-   href="#form0">form</a></code> content attribute, or, if there is no <code
-   title=form-attribute><a href="#form0">form</a></code> attribute, the
+   href="#form">form</a></code> content attribute, or, if there is no <code
+   title=form-attribute><a href="#form">form</a></code> attribute, the
    element's ancestors.
 
-  <p>The <dfn id=form1 title=dom-form><code>form</code></dfn> attribute on
+  <p>The <dfn id=form0 title=dom-form><code>form</code></dfn> attribute on
    most of the control interfaces is read-only, and shall return the first
    entry in the <code><a href="#forms">forms</a></code> list, unless that
    list is empty, in which case it returns null.
 
   <p>The <code><a href="#forms">forms</a></code> and <code title=dom-form><a
-   href="#form1">form</a></code> DOM attributes are live, so that adding a
+   href="#form0">form</a></code> DOM attributes are live, so that adding a
    form with an ID that was previously listed in a control's <code
-   title=form-attribute><a href="#form0">form</a></code> content attribute,
+   title=form-attribute><a href="#form">form</a></code> content attribute,
    for example, will cause that control to be associated with that form, and
    that form to appear in the DOM attributes.
 
   <p class=note>Since the <code title=dom-form><a
-   href="#form1">form</a></code> DOM attribute is read-only and the <code><a
+   href="#form0">form</a></code> DOM attribute is read-only and the <code><a
    href="#forms">forms</a></code> list is immutable, the way to dynamically
    change which forms a form control is associated with is to use the DOM
    Core attribute manipulation methods (e.g. <code>setAttribute()</code>).
@@ -7134,14 +7141,14 @@
    <code><a href="#htmllegendelement">HTMLLegendElement</a></code>s, and
    <code><a href="#htmllabelelement">HTMLLabelElement</a></code>s, the
    <code><a href="#forms">forms</a></code> and <code title=dom-form><a
-   href="#form1">form</a></code> DOM attributes shall reflect the attributes
+   href="#form0">form</a></code> DOM attributes shall reflect the attributes
    of their respective <code><a
    href="#htmlselectelement">HTMLSelectElement</a></code>, <code><a
    href="#htmlfieldsetelement">HTMLFieldSetElement</a></code>, or (for
    labels) their associated form control, if they have one, and shall return
    null and empty (respectively) if they don't.
 
-  <h3 id=additions2><span class=secno>7.9. </span>Additions specific to the
+  <h3 id=additions2><span class=secno>7.9 </span>Additions specific to the
    <code><a href="#htmlinputelement">HTMLInputElement</a></code> interface</h3>
 
   <p>The <dfn id=list0 title=dom-list><code>list</code></dfn> attribute is
@@ -7337,7 +7344,7 @@
    must be clamped to the nearest value that can be represented by the
    control.
 
-  <h3 id=the-defaultvalue><span class=secno>7.10. </span>The
+  <h3 id=the-defaultvalue><span class=secno>7.10 </span>The
    <code>defaultValue</code> DOM attribute</h3>
 
   <p>For <code><a href="#htmlinputelement">HTMLInputElement</a></code>
@@ -7368,7 +7375,7 @@
    affect the <code>value</code> DOM attribute, even if the user has not
    changed the value.
 
-  <h3 id=labels><span class=secno>7.11. </span>Labels</h3>
+  <h3 id=labels><span class=secno>7.11 </span>Labels</h3>
 
   <p>Form controls all have a <dfn id=labels0
    title=dom-labels><code>labels</code></dfn> DOM attribute that lists all
@@ -7393,7 +7400,7 @@
    do so, it should walk up the element's <code>parentNode</code> chain to
    find the <code>fieldset</code> ancestors.
 
-  <h3 id=firing><span class=secno>7.12. </span>Firing change events</h3>
+  <h3 id=firing><span class=secno>7.12 </span>Firing change events</h3>
 
   <p>The <dfn id=dispatchchange><code>dispatchChange()</code></dfn> and <dfn
    id=dispatchformchange0><code>dispatchFormChange()</code></dfn> methods
@@ -7415,7 +7422,7 @@
    href="#dispatchformchange">dispatchFormChange()</a></code> method on the
    <code><a href="#htmlformelement">HTMLFormElement</a></code> interface.
 
-  <h3 id=repetition1><span class=secno>7.13. </span>Repetition interfaces</h3>
+  <h3 id=repetition1><span class=secno>7.13 </span>Repetition interfaces</h3>
 
   <p>The <dfn id=repetitionelement0><code>RepetitionElement</code></dfn>
    interface must be implemented by all elements.
@@ -7518,7 +7525,7 @@
 
   <h2 id=presentation><span class=secno>8. </span>Presentation and rendering</h2>
 
-  <h3 id=styling-form-controls><span class=secno>8.1. </span>Styling form
+  <h3 id=styling-form-controls><span class=secno>8.1 </span>Styling form
    controls</h3>
 
   <p>The CSS working group is expected to develop a language designed,
@@ -7534,7 +7541,7 @@
   <p class=note>CSS 2.1 explicitly does not define how CSS applies to form
    controls. <a href="#refsCSS21">[CSS21]</a>
 
-  <h3 id=relation><span class=secno>8.2. </span>Relation to CSS selectors</h3>
+  <h3 id=relation><span class=secno>8.2 </span>Relation to CSS selectors</h3>
 
   <p>The W3C Selectors and CSS3 UI specifications define a number of
    pseudo-classes for form controls. <a href="#refsSelectors">[SELECTORS]</a>
@@ -7675,7 +7682,7 @@
    pseudo-classes given in CSS3 UI. This is intentional as the definitions
    given in CSS3 UI do not map well to the HTML semantics.
 
-  <h3 id=interaction><span class=secno>8.3. </span>Interaction of the form
+  <h3 id=interaction><span class=secno>8.3 </span>Interaction of the form
    processing model with CSS</h3>
 
   <p>There is no interaction between the form processing model and CSS. For
@@ -7685,7 +7692,7 @@
    href="#hidden">hidden</a></code> typically have <code>display: none</code>
    applied to them in the UA default style sheet.)
 
-  <h3 id=interaction0><span class=secno>8.4. </span>Interaction of the form
+  <h3 id=interaction0><span class=secno>8.4 </span>Interaction of the form
    processing model with SMIL</h3>
 
   <p>There is no interaction between the form processing model and SMIL.
@@ -7994,12 +8001,12 @@
    have an <code>onchange</code> attribute in the XHTML Intrinsic Events
    module. The <code>onformchange</code> and <code>onforminput</code>
    attributes are added to all form control elements (including <code><a
-   href="#output0">output</a></code>) and the <code>form</code> element. The
+   href="#output">output</a></code>) and the <code>form</code> element. The
    <code>oninvalid</code> attribute is added to all form controls except
-   <code><a href="#output0">output</a></code> and <code>button</code>
+   <code><a href="#output">output</a></code> and <code>button</code>
    elements. The <code>onchange</code> attribute (but not
    <code>oninput</code>) is added to the <code><a
-   href="#output0">output</a></code> element.
+   href="#output">output</a></code> element.
 
   <p>When frames and multiple windows are also allowed, the
    <code>target</code> attribute is added to the <code>form</code>,
@@ -8216,7 +8223,7 @@
      <td class=yes>Yes
 
     <tr>
-     <th><code><a href="#autofocus0">autofocus</a></code>
+     <th><code><a href="#autofocus">autofocus</a></code>
 
      <td class=yes>Yes
 




More information about the Commit-Watchers mailing list