- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 07 Nov 2008 05:32:57 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv28970
Modified Files:
Overview.html
Log Message:
WF2: Try to clear up when you fire input/change events. (whatwg r2391)
Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.1562
retrieving revision 1.1563
diff -u -d -r1.1562 -r1.1563
--- Overview.html 6 Nov 2008 21:49:41 -0000 1.1562
+++ Overview.html 7 Nov 2008 05:32:54 -0000 1.1563
@@ -8,7 +8,7 @@
<p><a href=http://www.w3.org/><img alt=W3C height=48 src=http://www.w3.org/Icons/w3c_home width=72></a></p>
<h1>HTML 5</h1>
<h2 class="no-num no-toc" id=a-vocabulary-and-associated-apis-for-html-and-xhtml>A vocabulary and associated APIs for HTML and XHTML</h2>
- <h2 class="no-num no-toc" id=editor-s-draft-date-zzz-9-june-2008><!-- "W3C Working Draft" --> Editor's Draft <!--ZZZ-->6 November 2008</h2>
+ <h2 class="no-num no-toc" id=editor-s-draft-date-zzz-9-june-2008><!-- "W3C Working Draft" --> Editor's Draft <!--ZZZ-->7 November 2008</h2>
<dl><!-- ZZZ: update the month/day
<dt>This Version:</dt>
<dd><a href="http://www.w3.org/TR/2008/WD-html5-20080610/">http://www.w3.org/TR/2008/WD-html5-20080610/</a></dd>
@@ -97,7 +97,7 @@
specification's progress along the W3C Recommendation
track.
<!--ZZZ:-->
- This specification is the 6 November 2008 <!--ZZZ "Working Draft"-->Editor's Draft.
+ This specification is the 7 November 2008 <!--ZZZ "Working Draft"-->Editor's Draft.
<!--:ZZZ-->
</p><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- relationship to other work (required) --><p>This specification is also being produced by the <a href=http://www.whatwg.org/>WHATWG</a>. The two specifications are
identical from the table of contents onwards.</p><!-- UNDER NO CIRCUMSTANCES IS THE FOLLOWING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- context and rationale (required) --><p>This specification is intended to replace (be a new version of)
@@ -21595,22 +21595,23 @@
<code><a href=#the-input-element>input</a></code> element's <a href=#concept-fe-value title=concept-fe-value>value</a>, if any. If there is no <a href=#concept-input-list title=concept-input-list>suggestions source element</a>, or if
it contains no matching <code><a href=#the-option-element>option</a></code> element, then the <code title=dom-input-selectedOption><a href=#dom-input-selectedoption>selectedOption</a></code> attribute
must return null.<h5 id=common-event-behaviors><span class=secno>4.10.4.4 </span>Common event behaviors</h5><p>When the <dfn id=event-input-input title=event-input-input><code>input</code></dfn>
- event applies, the user agent must <a href=#queue-a-task>queue a task</a> to
- <a href=#fire-a-simple-event>fire a simple event</a> called <code title=event-input>input</code> at the <code><a href=#the-input-element>input</a></code> element,
- then <a href=#broadcast-forminput-events>broadcast <code title=event-forminput>forminput</code>
- events</a> at the <code><a href=#the-input-element>input</a></code> element's <a href=#form-owner>form
- owner</a>, any time the user causes the element's <a href=#concept-fe-value title=concept-fe-value>value</a> to change. User agents may
- wait for a suitable break in the user's interaction before queuing
- the task; for example, a user agent could wait for the user to have
- not hit a key for 100ms, so as to only fire the event when the user
- pauses, instead of continuously for each keystroke.<p>When the <dfn id=event-input-change title=event-input-change><code>change</code></dfn> event applies,
+ event applies, any time the user causes the element's <a href=#concept-fe-value title=concept-fe-value>value</a> to change, the user agent must
+ <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple event</a> called
+ <code title=event-input>input</code> at the <code><a href=#the-input-element>input</a></code>
+ element, then <a href=#broadcast-forminput-events>broadcast <code title=event-forminput>forminput</code> events</a> at the
+ <code><a href=#the-input-element>input</a></code> element's <a href=#form-owner>form owner</a>. User agents
+ may wait for a suitable break in the user's interaction before
+ queuing the task; for example, a user agent could wait for the user
+ to have not hit a key for 100ms, so as to only fire the event when
+ the user pauses, instead of continuously for each keystroke.<p>When the <dfn id=event-input-change title=event-input-change><code>change</code></dfn> event applies,
if the element does not have an <a href=#activation-behavior>activation behavior</a>
defined but uses a user interface that involves an explicit commit
- action, then the user agent must <a href=#queue-a-task>queue a task</a> to
- <a href=#fire-a-simple-event>fire a simple event</a> called <code title=event-change>change</code> at the <code><a href=#the-input-element>input</a></code>
- element, then <a href=#broadcast-formchange-events>broadcast <code title=event-formchange>formchange</code> events</a> at the
- <code><a href=#the-input-element>input</a></code> element's <a href=#form-owner>form owner</a>, any time the
- user commits a change to the element's <a href=#concept-fe-value title=concept-fe-value>value</a> or list of <a href=#concept-input-type-file-selected title=concept-input-type-file-selected>selected files</a>.<p class=example>An example of a user interface with a commit
+ action, then any time the user commits a change to the element's
+ <a href=#concept-fe-value title=concept-fe-value>value</a> or list of <a href=#concept-input-type-file-selected title=concept-input-type-file-selected>selected files</a>, the
+ user agent must <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple
+ event</a> called <code title=event-change>change</code> at the
+ <code><a href=#the-input-element>input</a></code> element, then <a href=#broadcast-formchange-events>broadcast <code title=event-formchange>formchange</code> events</a> at the
+ <code><a href=#the-input-element>input</a></code> element's <a href=#form-owner>form owner</a>.<p class=example>An example of a user interface with a commit
action would be a <a href=#file-upload-state title=attr-input-type-file>File
Upload</a> control that consists of a single button that brings
up a file selection dialog: when the dialog is closed, if that the
@@ -21620,7 +21621,27 @@
control that allows both text-based user input and user selection
from a drop-down calendar: while text input might not have an
explicit commit step, selecting a date from the drop down calendar
- and then dismissing the drop down would be a commit action.<p class=note>In addition, when the <code title=event-input-change><a href=#event-input-change>change</a></code> event applies, <code title=event-change>change</code> events can also be fired as part
+ and then dismissing the drop down would be a commit action.<p>When the user agent changes the element's <a href=#concept-fe-value title=concept-fe-value>value</a> on behalf of the user (e.g. as
+ part of a form prefilling feature), the user agent must follow these
+ steps:<ol><li>If the <code title=event-input-input><a href=#event-input-input>input</a></code> event
+ applies, <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple
+ event</a> called <code title=event-input>input</code> at the
+ <code><a href=#the-input-element>input</a></code> element.</li>
+
+ <li>If the <code title=event-input-input><a href=#event-input-input>input</a></code> event
+ applies, <a href=#broadcast-forminput-events>broadcast <code title=event-forminput>forminput</code> events</a> at the
+ <code><a href=#the-input-element>input</a></code> element's <a href=#form-owner>form owner</a>.</li>
+
+ <li>If the <code title=event-input-change><a href=#event-input-change>change</a></code> event
+ applies, <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple
+ event</a> called <code title=event-change>change</code> at the
+ <code><a href=#the-input-element>input</a></code> element.</li>
+
+ <li>If the <code title=event-input-change><a href=#event-input-change>change</a></code> event
+ applies, <a href=#broadcast-formchange-events>broadcast <code title=event-formchange>formchange</code> events</a> at the
+ <code><a href=#the-input-element>input</a></code> element's <a href=#form-owner>form owner</a>.</li>
+
+ </ol><p class=note>In addition, when the <code title=event-input-change><a href=#event-input-change>change</a></code> event applies, <code title=event-change>change</code> events can also be fired as part
of the element's <a href=#activation-behavior>activation behavior</a> and as part of the
<a href=#unfocusing-steps>unfocusing steps</a>.<p>The <a href=#task-source>task source</a> for these <span title=concept-tasks>task</span> is the <a href=#user-interaction-task-source>user interaction task
source</a>.<h4 id=the-button-element><span class=secno>4.10.5 </span>The <dfn><code>button</code></dfn> element</h4><dl class=element><dt>Categories</dt>
Received on Friday, 7 November 2008 05:33:08 UTC