html5/spec Overview.html,1.1495,1.1496

Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv12903

Modified Files:
	Overview.html 
Log Message:
Clean up some stuff around the forms. (whatwg r2323)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.1495
retrieving revision 1.1496
diff -u -d -r1.1495 -r1.1496
--- Overview.html	11 Oct 2008 01:37:44 -0000	1.1495
+++ Overview.html	11 Oct 2008 01:51:41 -0000	1.1496
@@ -20919,7 +20919,7 @@
   the user returns to the page, the UA can prefill the form. When an
   <code><a href=#the-input-element>input</a></code> element's <code title=attr-input-autocomplete><a href=#attr-input-autocomplete>autocomplete</a></code> attribute is in
   the <a href=#attr-input-autocomplete-off-state title=attr-input-autocomplete-off-state>off</a>
-  state, the user agent should not remember the control's value.</p><!-- XXX xref value? --><p>The autocompletion mechanism must be implemented by the user
+  state, the user agent should not remember the control's <a href=#concept-fe-value title=concept-fe-value>value</a>.<p>The autocompletion mechanism must be implemented by the user
   agent acting as if the user had modified the element's <a href=#concept-fe-value title=concept-fe-value>value</a>, and must be done at a time
   where the element is <i title=concept-input-mutable><a href=#concept-input-mutable>mutable</a></i>
   (e.g. just after the element has been inserted into the document, or
@@ -21040,8 +21040,7 @@
   value (its <a href=#concept-input-min title=concept-input-min>minimum</a>).<p class=note>If an element has a <a href=#attr-input-max title=attr-input-max>maximum</a> that is less than its <a href=#attr-input-min title=attr-input-min>minimum</a>, then so long as the element
   has a <a href=#concept-fe-value title=concept-fe-value>value</a>, it will either be
   <a href=#suffering-from-an-underflow>suffering from an underflow</a> or <a href=#suffering-from-an-overflow>suffering from an
-  overflow</a>.<h6 id=the-step-attribute><span class=secno>4.10.4.2.9 </span>The <code title=attr-input-step><a href=#attr-input-step>step</a></code> attribute</h6><!-- XXX this is defined to be a floating point number, which is a
-  little odd for type=date, type=month, and type=week --><p>The <dfn id=attr-input-step title=attr-input-step><code>step</code></dfn>
+  overflow</a>.<h6 id=the-step-attribute><span class=secno>4.10.4.2.9 </span>The <code title=attr-input-step><a href=#attr-input-step>step</a></code> attribute</h6><p>The <dfn id=attr-input-step title=attr-input-step><code>step</code></dfn>
   attribute indicates the granularity that is expected (and required)
   of the <a href=#concept-fe-value title=concept-fe-value>value</a>, by limiting
   the allowed values. The section that defines the <code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute's current state also
@@ -21130,9 +21129,7 @@
   string; otherwise, run the <a href=#concept-input-value-date-string title=concept-input-value-date-string>algorithm to convert a
   <code>Date</code> object to a string</a>, as defined for that
   state, on the new value, and set the <a href=#concept-fe-value title=concept-fe-value>value</a> of the element to resulting
-  string.</p><hr><!-- XXX should simplify this stuff. The only reason we defer to the
-  Date stuff here is type=month; can we make things simpler somehow?
-  --><p>The <dfn id=dom-input-valueasnumber title=dom-input-valueAsNumber><code>valueAsNumber</code></dfn> DOM
+  string.</p><hr><p>The <dfn id=dom-input-valueasnumber title=dom-input-valueAsNumber><code>valueAsNumber</code></dfn> DOM
   attribute represents the <a href=#concept-fe-value title=concept-fe-value>value</a>
   of the element, interpreted as a number.<p>On getting, if the <code title=dom-input-valueAsNumber><a href=#dom-input-valueasnumber>valueAsNumber</a></code> attribute does
   not apply, as defined for the <code><a href=#the-input-element>input</a></code> element's <code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute's current state, then
@@ -22232,7 +22229,7 @@
   agent would show the user if this were the only form with a validity
   constraint problem. If the element is <a href=#suffering-from-a-custom-error>suffering from a custom
   error</a>, then the <a href=#custom-validity-error-message>custom validity error message</a>
-  should be present in the return value.<h4 id=form-submission-0><span class=secno>4.10.15 </span>Form submission</h4><!-- XXX http://lxr.mozilla.org/mozilla/source/content/html/content/src/nsHTMLFormElement.cpp --><p>When a form <var title="">form</var> is <dfn id=concept-form-submit title=concept-form-submit>submitted</dfn> from an element <var title="">submitter</var> (typically a button), the user agent must
+  should be present in the return value.<h4 id=form-submission-0><span class=secno>4.10.15 </span>Form submission</h4><p>When a form <var title="">form</var> is <dfn id=concept-form-submit title=concept-form-submit>submitted</dfn> from an element <var title="">submitter</var> (typically a button), the user agent must
   run the following steps:<ol><li id=sandboxSubmitBlocked><p>If <var title="">form</var> is in
    a <code>Document</code> that has no associated <a href=#browsing-context>browsing
    context</a> or whose <a href=#browsing-context>browsing context</a> has its
@@ -22249,11 +22246,11 @@
 
    <li><p>If the <var title="">submitter</var> is anything but a
    <code><a href=#the-form-element>form</a></code> element, then <a href=#fire-a-simple-event>fire a simple event</a>
-   that bubbles<!--XXX-->, named <code title=event-submit>submit</code>, at <var title="">form</var>. If
+   that bubbles<!--XXX check it bubbles-->, named <code title=event-submit>submit</code>, at <var title="">form</var>. If
    the event's default action is prevented (i.e. if the event is
    canceled) then abort these steps. Otherwise, continue (effectively
-   the default action is to perform the submission).</li>
-   <!-- XXX define what happens if .submit() is called during this -->
+   the default action is to perform the submission).</li> <!-- XXX
+   define what happens if .submit() is called during this -->
 
    <li><p>Let <var title="">controls</var> be a list of all the <a href=#category-submit title=category-submit>submittable</a> elements whose
    <a href=#form-owner>form owner</a> is <var title="">form</var>, in <a href=#tree-order>tree
@@ -22879,7 +22876,8 @@
    <a href=#tree-order>tree order</a>, <a href=#fire-a-simple-event>fire a simple event</a> named
    <var title="">event name</var> at the element.</li>
 
-  </ol><h3 id=interactive-elements><span class=secno>4.11 </span>Interactive elements</h3><h4 id=the-details-element><span class=secno>4.11.1 </span>The <dfn><code>details</code></dfn> element</h4><dl class=element><dt>Categories</dt>
+  </ol><p class=XXX>Still need to define when formchange and forminput
+  fire naturally.<h3 id=interactive-elements><span class=secno>4.11 </span>Interactive elements</h3><h4 id=the-details-element><span class=secno>4.11.1 </span>The <dfn><code>details</code></dfn> element</h4><dl class=element><dt>Categories</dt>
    <dd><a href=#flow-content-0>Flow content</a>.</dd>
    <dd><a href=#interactive-content-0>Interactive content</a>.</dd>
    <dt>Contexts in which this element may be used:</dt>

Received on Saturday, 11 October 2008 01:51:53 UTC