hixie: try to clarify this section a little (whatwg r5213)

hixie: try to clarify this section a little (whatwg r5213)

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.4147&r2=1.4148&f=h
http://html5.org/tools/web-apps-tracker?from=5212&to=5213

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.4147
retrieving revision 1.4148
diff -u -d -r1.4147 -r1.4148
--- Overview.html 27 Jul 2010 23:38:07 -0000 1.4147
+++ Overview.html 28 Jul 2010 00:01:19 -0000 1.4148
@@ -308,7 +308,7 @@
 
    <h1>HTML5</h1>
    <h2 class="no-num no-toc" id="a-vocabulary-and-associated-apis-for-html-and-xhtml">A vocabulary and associated APIs for HTML and XHTML</h2>
-   <h2 class="no-num no-toc" id="editor-s-draft-27-july-2010">Editor's Draft 27 July 2010</h2>
+   <h2 class="no-num no-toc" id="editor-s-draft-28-july-2010">Editor's Draft 28 July 2010</h2>
    <dl><dt>Latest Published Version:</dt>
     <dd><a href="http://www.w3.org/TR/html5/">http://www.w3.org/TR/html5/</a></dd>
     <dt>Latest Editor's Draft:</dt>
@@ -414,7 +414,7 @@
   Group</a> is the W3C working group responsible for this
   specification's progress along the W3C Recommendation
   track.
-  This specification is the 27 July 2010 Editor's Draft.
+  This specification is the 28 July 2010 Editor's Draft.
   </p><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- relationship to other work (required) --><p>Work on this specification is also done at the <a href="http://www.whatwg.org/">WHATWG</a>. The W3C HTML working group
   actively pursues convergence with the WHATWG, as required by the <a href="http://www.w3.org/2007/03/HTML-WG-charter">W3C HTML working
   group charter</a>.</p><!-- UNDER NO CIRCUMSTANCES IS THE FOLLOWING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- required patent boilerplate --><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5
@@ -33477,11 +33477,22 @@
   <dfn id="form-owner">form owner</dfn>. If a <a href="#form-associated-element">form-associated element</a> is
   not associated with a <code><a href="#the-form-element">form</a></code> element, its <a href="#form-owner">form
   owner</a> is said to be null.<p>A <a href="#form-associated-element">form-associated element</a> is, by default, associated
-  with its nearest ancestor <code><a href="#the-form-element">form</a></code> element<span class="impl"> (as described below)</span>, but may have a <dfn id="attr-fae-form" title="attr-fae-form"><code>form</code></dfn> attribute specified to
+  with its <span class="impl">nearest</span> ancestor
+  <code><a href="#the-form-element">form</a></code> element<span class="impl"> (as described
+  below)</span>, but may have a <dfn id="attr-fae-form" title="attr-fae-form"><code>form</code></dfn> attribute specified to
   override this.<p>If a <a href="#form-associated-element">form-associated element</a> has a <code title="attr-fae-form"><a href="#attr-fae-form">form</a></code> attribute specified, then its
   value must be the ID of a <code><a href="#the-form-element">form</a></code> element in the element's
   owner <code><a href="#document">Document</a></code>.<div class="impl">
 
+  <p class="note">The rules in this section are complicated by the
+  fact that although conforming documents will never contain nested
+  <code><a href="#the-form-element">form</a></code> elements, it is quite possible (e.g. using a
+  script that performs DOM manipulation) to generate documents that
+  have such nested elements. They are also complicated by rules in the
+  HTML parser that, for historical reasons, can result in a
+  <a href="#form-associated-element">form-associated element</a> being associated with a
+  <code><a href="#the-form-element">form</a></code> element that is not its ancestor.</p>
+
   <p>When a <a href="#form-associated-element">form-associated element</a> is created, its
   <a href="#form-owner">form owner</a> must be initialized to null (no owner).</p>

Received on Wednesday, 28 July 2010 00:02:18 UTC