[e] (0) More clarifications.

git-svn-id: http://svn.whatwg.org/webapps@5266 340c8d12-0b0e-0410-8428-c7bf67bfef74
whatwg · Aug 10, 2010 · 96867df · 96867df
1 parent cdd77a3
commit 96867df
Show file tree

Hide file tree

Showing 3 changed files with 27 additions and 24 deletions.
diff --git a/complete.html b/complete.html
@@ -44627,11 +44627,12 @@ <h4 id=association-of-controls-and-forms><span class=secno>4.10.18 </span>Associ
    form "c", while the <a href=#form-owner>form owner</a> of "e" would be the
    outer form "a".</p>
 
-   <p>This is because despite the association of "e" with "c" in the
-   <a href=#html-parser>HTML parser</a>, when the <code title=dom-innerHTML><a href=#dom-innerhtml>innerHTML</a></code> algorithm moves the nodes
-   from the temporary document to the "b" element, the nodes see their
-   ancestor chain change, and thus all the "magic" associations done
-   by the parser are reset to normal ancestor associations.</p>
+   <p>This happens as follows: First, the "e" node gets associated
+   with "c" in the <a href=#html-parser>HTML parser</a>. Theh, the <code title=dom-innerHTML><a href=#dom-innerhtml>innerHTML</a></code> algorithm moves the nodes
+   from the temporary document to the "b" element. At this point, the
+   nodes see their ancestor chain change, and thus all the "magic"
+   associations done by the parser are reset to normal ancestor
+   associations.</p>
 
    <p>This example is a non-conforming document, though, as it is a
    violation of the content models to nest <code><a href=#the-form-element>form</a></code>
@@ -46201,9 +46202,9 @@ <h5 id=plain-text-form-data><span class=secno>4.10.21.6 </span>Plain text form d
     <p>If the <code><a href=#the-form-element>form</a></code> element has an <code title=attr-form-accept-charset><a href=#attr-form-accept-charset>accept-charset</a></code> attribute,
     then, taking into account the characters found in the <var title="">form data set</var>'s names and values, and the character
     encodings supported by the user agent, select a character encoding
-    from the list given in the <code><a href=#the-form-element>form</a></code>'s <code title=attr-form-accept-charset><a href=#attr-form-accept-charset>accept-charset</a></code>
-    attribute. If none of the encodings are supported, then let the
-    selected character encoding be UTF-8.</p>
+    from the list given in the <code><a href=#the-form-element>form</a></code>'s <code title=attr-form-accept-charset><a href=#attr-form-accept-charset>accept-charset</a></code> attribute.
+    If none of the encodings are supported, or if none are listed,
+    then let the selected character encoding be UTF-8.</p>
 
     <p>Otherwise, the selected character encoding is the
     <a href="#document's-character-encoding">document's character encoding</a>.</p>

diff --git a/index b/index
@@ -44554,11 +44554,12 @@ out of 233&thinsp;257&thinsp;824 bytes available&lt;/meter&gt;&lt;/p&gt;</pre>
    form "c", while the <a href=#form-owner>form owner</a> of "e" would be the
    outer form "a".</p>
 
-   <p>This is because despite the association of "e" with "c" in the
-   <a href=#html-parser>HTML parser</a>, when the <code title=dom-innerHTML><a href=#dom-innerhtml>innerHTML</a></code> algorithm moves the nodes
-   from the temporary document to the "b" element, the nodes see their
-   ancestor chain change, and thus all the "magic" associations done
-   by the parser are reset to normal ancestor associations.</p>
+   <p>This happens as follows: First, the "e" node gets associated
+   with "c" in the <a href=#html-parser>HTML parser</a>. Theh, the <code title=dom-innerHTML><a href=#dom-innerhtml>innerHTML</a></code> algorithm moves the nodes
+   from the temporary document to the "b" element. At this point, the
+   nodes see their ancestor chain change, and thus all the "magic"
+   associations done by the parser are reset to normal ancestor
+   associations.</p>
 
    <p>This example is a non-conforming document, though, as it is a
    violation of the content models to nest <code><a href=#the-form-element>form</a></code>
@@ -46128,9 +46129,9 @@ fur
     <p>If the <code><a href=#the-form-element>form</a></code> element has an <code title=attr-form-accept-charset><a href=#attr-form-accept-charset>accept-charset</a></code> attribute,
     then, taking into account the characters found in the <var title="">form data set</var>'s names and values, and the character
     encodings supported by the user agent, select a character encoding
-    from the list given in the <code><a href=#the-form-element>form</a></code>'s <code title=attr-form-accept-charset><a href=#attr-form-accept-charset>accept-charset</a></code>
-    attribute. If none of the encodings are supported, then let the
-    selected character encoding be UTF-8.</p>
+    from the list given in the <code><a href=#the-form-element>form</a></code>'s <code title=attr-form-accept-charset><a href=#attr-form-accept-charset>accept-charset</a></code> attribute.
+    If none of the encodings are supported, or if none are listed,
+    then let the selected character encoding be UTF-8.</p>
 
     <p>Otherwise, the selected character encoding is the
     <a href="#document's-character-encoding">document's character encoding</a>.</p>

diff --git a/source b/source
@@ -49959,12 +49959,13 @@ out of 233&#x2009;257&#x2009;824 bytes available&lt;/meter>&lt;/p></pre>
    form "c", while the <span>form owner</span> of "e" would be the
    outer form "a".</p>
 
-   <p>This is because despite the association of "e" with "c" in the
-   <span>HTML parser</span>, when the <code
+   <p>This happens as follows: First, the "e" node gets associated
+   with "c" in the <span>HTML parser</span>. Theh, the <code
    title="dom-innerHTML">innerHTML</code> algorithm moves the nodes
-   from the temporary document to the "b" element, the nodes see their
-   ancestor chain change, and thus all the "magic" associations done
-   by the parser are reset to normal ancestor associations.</p>
+   from the temporary document to the "b" element. At this point, the
+   nodes see their ancestor chain change, and thus all the "magic"
+   associations done by the parser are reset to normal ancestor
+   associations.</p>
 
    <p>This example is a non-conforming document, though, as it is a
    violation of the content models to nest <code>form</code>
@@ -51869,9 +51870,9 @@ fur
     title="">form data set</var>'s names and values, and the character
     encodings supported by the user agent, select a character encoding
     from the list given in the <code>form</code>'s <code
-    title="attr-form-accept-charset">accept-charset</code>
-    attribute. If none of the encodings are supported, then let the
-    selected character encoding be UTF-8.</p>
+    title="attr-form-accept-charset">accept-charset</code> attribute.
+    If none of the encodings are supported, or if none are listed,
+    then let the selected character encoding be UTF-8.</p>
 
     <p>Otherwise, the selected character encoding is the
     <span>document's character encoding</span>.</p>