html5/spec association-of-controls-and-forms.html,1.14,1.15 forms.html,1.994,1.995 spec.html,1.1120,1.1121 tabular-data.html,1.990,1.991 from Michael Smith via cvs-syncmail on 2010-08-10 (public-html-commits@w3.org from August 2010)

From: Michael Smith via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 10 Aug 2010 02:06:44 +0000
To: public-html-commits@w3.org
Message-Id: <E1OieEm-0000db-Rg@lionel-hutz.w3.org>
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv2399

Modified Files:
	association-of-controls-and-forms.html forms.html spec.html 
	tabular-data.html 
Log Message:
clarifications (whatwg r5264)

[updated by splitter]


Index: tabular-data.html
===================================================================
RCS file: /sources/public/html5/spec/tabular-data.html,v
retrieving revision 1.990
retrieving revision 1.991
diff -u -d -r1.990 -r1.991
--- tabular-data.html	9 Aug 2010 23:17:09 -0000	1.990
+++ tabular-data.html	10 Aug 2010 02:06:42 -0000	1.991
@@ -329,10 +329,10 @@
    <dd>Where <a href="content-models.html#flow-content">flow content</a> is expected.</dd>
    <dt>Content model:</dt>
    <dd>In this order: optionally a <code><a href="#the-caption-element">caption</a></code> element,
-   followed by either zero or more <code><a href="#the-colgroup-element">colgroup</a></code> elements,
-   followed optionally by a <code><a href="#the-thead-element">thead</a></code> element, followed
-   optionally by a <code><a href="#the-tfoot-element">tfoot</a></code> element, followed by either zero
-   or more <code><a href="#the-tbody-element">tbody</a></code> elements or one or more <code><a href="#the-tr-element">tr</a></code>
+   followed by zero or more <code><a href="#the-colgroup-element">colgroup</a></code> elements, followed
+   optionally by a <code><a href="#the-thead-element">thead</a></code> element, followed optionally by
+   a <code><a href="#the-tfoot-element">tfoot</a></code> element, followed by either zero or more
+   <code><a href="#the-tbody-element">tbody</a></code> elements or one or more <code><a href="#the-tr-element">tr</a></code>
    elements, followed optionally by a <code><a href="#the-tfoot-element">tfoot</a></code> element (but
    there can only be one <code><a href="#the-tfoot-element">tfoot</a></code> element child in
    total).</dd>

Index: association-of-controls-and-forms.html
===================================================================
RCS file: /sources/public/html5/spec/association-of-controls-and-forms.html,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -d -r1.14 -r1.15
--- association-of-controls-and-forms.html	10 Aug 2010 01:36:49 -0000	1.14
+++ association-of-controls-and-forms.html	10 Aug 2010 02:06:42 -0000	1.15
@@ -332,9 +332,9 @@
   with its <span class="impl">nearest</span> ancestor
   <code><a href="forms.html#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><p>If a <a href="forms.html#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="forms.html#the-form-element">form</a></code> element in the element's
-  owner <code><a href="infrastructure.html#document">Document</a></code>.</p><div class="impl">
+  override this.</p><p>If a <a href="forms.html#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 that
+  attribute's value must be the ID of a <code><a href="forms.html#the-form-element">form</a></code> element in
+  the element's owner <code><a href="infrastructure.html#document">Document</a></code>.</p><div class="impl">
 
   <p class="note">The rules in this section are complicated by the
   fact that although conforming documents will never contain nested
@@ -1085,8 +1085,8 @@
 
   <h5 id="introduction-1"><span class="secno">4.10.21.1 </span>Introduction</h5><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i></p>
 
-  </div><p><i>This section is non-normative.</i></p><p>When forms are submitted, the data in the form is converted into
-  the form specified by the <a href="#concept-fs-enctype" title="concept-fs-enctype">enctype</a>, and then sent to the
+  </div><p><i>This section is non-normative.</i></p><p>When a form is submitted, the data in the form is converted into
+  the structure specified by the <a href="#concept-fs-enctype" title="concept-fs-enctype">enctype</a>, and then sent to the
   destination specified by the <a href="#concept-fs-action" title="concept-fs-action">action</a> using the given <a href="#concept-fs-method" title="concept-fs-method">method</a>.</p><p>For example, take the following form:</p><pre>&lt;form action="/find.cgi" method=get&gt;
  &lt;input type=text name=t&gt;
  &lt;input type=search name=q&gt;

Index: forms.html
===================================================================
RCS file: /sources/public/html5/spec/forms.html,v
retrieving revision 1.994
retrieving revision 1.995
diff -u -d -r1.994 -r1.995
--- forms.html	9 Aug 2010 23:17:06 -0000	1.994
+++ forms.html	10 Aug 2010 02:06:42 -0000	1.995
@@ -323,12 +323,14 @@
     <ol><li><a href="forms.html#introduction-0"><span class="secno">4.10.1 </span>Introduction</a>
       <ol><li><a href="forms.html#writing-a-form-s-user-interface"><span class="secno">4.10.1.1 </span>Writing a form's user interface</a></li><li><a href="forms.html#implementing-the-server-side-processing-for-a-form"><span class="secno">4.10.1.2 </span>Implementing the server-side processing for a form</a></li><li><a href="forms.html#configuring-a-form-to-communicate-with-a-server"><span class="secno">4.10.1.3 </span>Configuring a form to communicate with a server</a></li><li><a href="forms.html#client-side-form-validation"><span class="secno">4.10.1.4 </span>Client-side form validation</a></li></ol></li><li><a href="forms.html#categories"><span class="secno">4.10.2 </span>Categories</a></li><li><a href="forms.html#the-form-element"><span class="secno">4.10.3 </span>The <code>form</code> element</a></li><li><a href="forms.html#the-fieldset-element"><span class="secno">4.10.4 </span>The <code>fieldset</code> element</a></li><li><a href="forms.html#the-legend-element"><span class="secno">4.10.5 </span>The code>legend</code> element</a></li><li><a href="forms.html#the-label-element"><span class="secno">4.10.6 </span>The <code>label</code> element</a></li></ol></li></ol></li></ol></div>
 
-  <h3 id="forms"><span class="secno">4.10 </span>Forms</h3><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i></p><h4 id="introduction-0"><span class="secno">4.10.1 </span>Introduction</h4><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i></p><p><i>This section is non-normative.</i></p><p>Forms allow unscripted client-server interaction: given a form, a
-  user can provide data, submit it to the server, and have the server
-  act on it accordingly (e.g. returning the results of a search or
-  calculation). The elements used in forms can also be used for user
-  interaction with no associated submission mechanism, in conjunction
-  with scripts.</p><p>Writing a form consists of several steps, which can be performed
+  <h3 id="forms"><span class="secno">4.10 </span>Forms</h3><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i></p><h4 id="introduction-0"><span class="secno">4.10.1 </span>Introduction</h4><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i></p><p><i>This section is non-normative.</i></p><p>A form is a component of a Web page that has form controls, such
+  as text fields, buttons, check boxes, range controls, or color
+  pickers. A user can interact with such a form, providing data that
+  can then be sent to the server for further processing (e.g.
+  returning the results of a search or calculation). No client-side
+  scripting is needed in many cases, though an API is available so
+  that scripts can augment the user experience or use forms for
+  purposes other than submitting data to a server.</p><p>Writing a form consists of several steps, which can be performed
   in any order: writing the user interface, implementing the
   server-side processing, and configuring the user interface to
   communicate with the server.</p><h5 id="writing-a-form-s-user-interface"><span class="secno">4.10.1.1 </span>Writing a form's user interface</h5><p><i>This section is non-normative.</i></p><p>For the purposes of this brief introduction, we will create a

Index: spec.html
===================================================================
RCS file: /sources/public/html5/spec/spec.html,v
retrieving revision 1.1120
retrieving revision 1.1121
diff -u -d -r1.1120 -r1.1121
--- spec.html	10 Aug 2010 01:36:49 -0000	1.1120
+++ spec.html	10 Aug 2010 02:06:42 -0000	1.1121
@@ -334,7 +334,7 @@
     <a href="Overview.html">single page HTML</a>,
     <a href="spec.html">multipage HTML</a>,
     <a href="author/">author edition</a>.
-This is revision 1.4191.
+This is revision 1.4193.
    </p> 
      <p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a>
    &#169; 2010 <a href="http://www.w3.org/"><abbr title="World Wide
Received on Tuesday, 10 August 2010 02:06:48 UTC