[html5] r2323 - [e] (0) Clean up some stuff around the forms.
whatwg at whatwg.org
whatwg at whatwg.org
Fri Oct 10 18:51:37 PDT 2008
Author: ianh
Date: 2008-10-10 18:51:37 -0700 (Fri, 10 Oct 2008)
New Revision: 2323
Modified:
index
source
Log:
[e] (0) Clean up some stuff around the forms.
Modified: index
===================================================================
--- index 2008-10-11 01:37:38 UTC (rev 2322)
+++ index 2008-10-11 01:51:37 UTC (rev 2323)
@@ -25770,8 +25770,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? -->
+ state, the user agent should not remember the control's <a href=#concept-fe-value title=concept-fe-value>value</a>.</p>
<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
@@ -25991,9 +25990,6 @@
<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>
attribute indicates the granularity that is expected (and required)
of the <a href=#concept-fe-value title=concept-fe-value>value</a>, by limiting
@@ -26110,9 +26106,7 @@
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
+ <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>
@@ -27608,8 +27602,6 @@
<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
run the following steps:</p>
@@ -27629,11 +27621,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
@@ -28290,8 +28282,13 @@
<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>
+ </ol><p class=XXX>Still need to define when formchange and forminput
+ fire naturally.</p>
+
+
+ <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>
Modified: source
===================================================================
--- source 2008-10-11 01:37:38 UTC (rev 2322)
+++ source 2008-10-11 01:51:37 UTC (rev 2323)
@@ -28754,8 +28754,8 @@
<code>input</code> element's <code
title="attr-input-autocomplete">autocomplete</code> attribute is in
the <span title="attr-input-autocomplete-off-state">off</span>
- state, the user agent should not remember the control's value.</p>
- <!-- XXX xref value? -->
+ state, the user agent should not remember the control's <span
+ title="concept-fe-value">value</span>.</p>
<p>The autocompletion mechanism must be implemented by the user
agent acting as if the user had modified the element's <span
@@ -29022,9 +29022,6 @@
<h6>The <code title="attr-input-step">step</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 title="attr-input-step"><code>step</code></dfn>
attribute indicates the granularity that is expected (and required)
of the <span title="concept-fe-value">value</span>, by limiting
@@ -29192,10 +29189,6 @@
<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
title="dom-input-valueAsNumber"><code>valueAsNumber</code></dfn> DOM
attribute represents the <span title="concept-fe-value">value</span>
@@ -31062,8 +31055,6 @@
<h4>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
title="concept-form-submit">submitted</dfn> from an element <var
title="">submitter</var> (typically a button), the user agent must
@@ -31087,12 +31078,12 @@
<li><p>If the <var title="">submitter</var> is anything but a
<code>form</code> element, then <span>fire a simple event</span>
- that bubbles<!--XXX-->, named <code
+ 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).</p></li>
- <!-- XXX define what happens if .submit() is called during this -->
+ the default action is to perform the submission).</p></li> <!-- XXX
+ define what happens if .submit() is called during this -->
<li><p>Let <var title="">controls</var> be a list of all the <span
title="category-submit">submittable</span> elements whose
@@ -31934,8 +31925,11 @@
</ol>
+ <p class="XXX">Still need to define when formchange and forminput
+ fire naturally.</p>
+
<h3 id="interactive-elements">Interactive elements</h3>
<h4>The <dfn><code>details</code></dfn> element</h4>
More information about the Commit-Watchers
mailing list