[html5] r5263 - [e] (0) Rewrite the form intro. Let me know if there's anything in the old intro [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2010-08-09 18:59:00 -0700 (Mon, 09 Aug 2010)
New Revision: 5263

Modified:
   complete.html
   index
   source
Log:
[e] (0) Rewrite the form intro. Let me know if there's anything in the old intro you think I should have kept.

Modified: complete.html
===================================================================
--- complete.html	2010-08-10 01:36:01 UTC (rev 5262)
+++ complete.html	2010-08-10 01:59:00 UTC (rev 5263)
@@ -33468,10 +33468,10 @@
    <dd>Where <a href=#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>
@@ -35932,12 +35932,14 @@
 
   <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>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

Modified: index
===================================================================
--- index	2010-08-10 01:36:01 UTC (rev 5262)
+++ index	2010-08-10 01:59:00 UTC (rev 5263)
@@ -33395,10 +33395,10 @@
    <dd>Where <a href=#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>
@@ -35859,12 +35859,14 @@
 
   <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>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

Modified: source
===================================================================
--- source	2010-08-10 01:36:01 UTC (rev 5262)
+++ source	2010-08-10 01:59:00 UTC (rev 5263)
@@ -36988,10 +36988,10 @@
    <dd>Where <span>flow content</span> is expected.</dd>
    <dt>Content model:</dt>
    <dd>In this order: optionally a <code>caption</code> element,
-   followed by either zero or more <code>colgroup</code> elements,
-   followed optionally by a <code>thead</code> element, followed
-   optionally by a <code>tfoot</code> element, followed by either zero
-   or more <code>tbody</code> elements or one or more <code>tr</code>
+   followed by zero or more <code>colgroup</code> elements, followed
+   optionally by a <code>thead</code> element, followed optionally by
+   a <code>tfoot</code> element, followed by either zero or more
+   <code>tbody</code> elements or one or more <code>tr</code>
    elements, followed optionally by a <code>tfoot</code> element (but
    there can only be one <code>tfoot</code> element child in
    total).</dd>
@@ -39928,12 +39928,14 @@
 
   <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>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