- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 10 Aug 2010 01:59:10 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv1556
Modified Files:
Overview.html
Log Message:
Rewrite the form intro. Let me know if there's anything in the old intro you think I should have kept. (whatwg r5263)
Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.4191
retrieving revision 1.4192
diff -u -d -r1.4191 -r1.4192
--- Overview.html 10 Aug 2010 01:36:05 -0000 1.4191
+++ Overview.html 10 Aug 2010 01:59:06 -0000 1.4192
@@ -23835,10 +23835,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>
@@ -26083,12 +26083,14 @@
<td> $ 3,761 <td> $ 2,963 <td> $ 2,433
<tr><th scope="row"> Percentage of net sales
<td> 11.6% <td> 12.3% <td> 12.6%
- </table><h3 id="forms"><span class="secno">4.10 </span>Forms</h3><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i><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><i>This section is non-normative.</i><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>Writing a form consists of several steps, which can be performed
+ </table><h3 id="forms"><span class="secno">4.10 </span>Forms</h3><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i><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><i>This section is non-normative.</i><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>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.<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>For the purposes of this brief introduction, we will create a
Received on Tuesday, 10 August 2010 01:59:11 UTC