W3C home > Mailing lists > Public > public-html-commits@w3.org > July 2009

html5/spec Overview.html,1.2675,1.2676

From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
Date: Mon, 27 Jul 2009 23:11:16 +0000
To: public-html-commits@w3.org
Message-Id: <E1MVZLg-0007u5-G6@lionel-hutz.w3.org>
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv30367

Modified Files:
	Overview.html 
Log Message:
Make 'input' and 'change' events bubble. (whatwg r3473)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2675
retrieving revision 1.2676
diff -u -d -r1.2675 -r1.2676
--- Overview.html	27 Jul 2009 22:09:59 -0000	1.2675
+++ Overview.html	27 Jul 2009 23:11:13 -0000	1.2676
@@ -28666,7 +28666,7 @@
   the element's <code title="dom-input-indeterminate"><a href="#dom-input-indeterminate">indeterminate</a></code> DOM attribute
   back to the values they had before the <a href="#pre-click-activation-steps">pre-click activation
   steps</a> were run. The <a href="#activation-behavior">activation behavior</a> is to
-  <a href="#fire-a-simple-event">fire a simple event</a> called <code title="event-change">change</code> at the element<!-- It's not
+  <a href="#fire-a-simple-event">fire a simple event</a> that bubbles called <code title="event-change">change</code> at the element<!-- It's not
   cancelable. Once this fires, the control is checked, end of
   story. -->, then <a href="#broadcast-formchange-events">broadcast <code title="event-formchange">formchange</code> events</a> at the
   element's <a href="#form-owner">form owner</a>.</p>
@@ -28785,9 +28785,9 @@
   true. The <a href="#canceled-activation-steps">canceled activation steps</a> consist of setting
   the element's <a href="#concept-fe-checked" title="concept-fe-checked">checkedness</a> to
   false. The <a href="#activation-behavior">activation behavior</a> is to <a href="#fire-a-simple-event">fire a
-  simple event</a> called <code title="event-change">change</code>
-  at the element<!-- It's not cancelable. Once this fires, the control
-  is checked, end of story. -->, then <a href="#broadcast-formchange-events">broadcast <code title="event-formchange">formchange</code> events</a> at the
+  simple event</a> that bubbles called <code title="event-change">change</code> at the element<!-- It's not
+  cancelable. Once this fires, the control is checked, end of
+  story. -->, then <a href="#broadcast-formchange-events">broadcast <code title="event-formchange">formchange</code> events</a> at the
   element's <a href="#form-owner">form owner</a>.</p>
 
   <p><strong>Constraint validation</strong>: If the element is <i title="concept-input-required"><a href="#concept-input-required">required</a></i> and all of the
@@ -29927,9 +29927,9 @@
 
   <p>When the <dfn id="event-input-input" title="event-input-input"><code>input</code></dfn>
   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
+  <a href="#queue-a-task">queue a task</a> to <a href="#fire-a-simple-event">fire a simple event</a> that
+  bubbles 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
@@ -29950,8 +29950,8 @@
   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
+  event</a> that bubbles 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>
 
   <p class="example">An example of a user interface with a commit
@@ -29974,8 +29974,8 @@
 
   <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>
+   event</a> that bubbles 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
@@ -29983,8 +29983,8 @@
 
    <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>
+   event</a> that bubbles 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
@@ -30214,7 +30214,8 @@
   <span title="event-click">click</span> event), the user agent must
   set the <a href="#concept-option-selectedness" title="concept-option-selectedness">selectedness</a> of the
   picked <code><a href="#the-option-element">option</a></code> element to true and then <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-select-element">select</a></code>
+  task</a> to <a href="#fire-a-simple-event">fire a simple event</a> that bubbles called
+  <code title="event-change">change</code> at the <code><a href="#the-select-element">select</a></code>
   element, using the <a href="#user-interaction-task-source">user interaction task source</a> as the
   task source, then <a href="#broadcast-formchange-events">broadcast <code title="event-formchange">formchange</code> events</a> at the
   element's <a href="#form-owner">form owner</a>.</p>
@@ -30248,10 +30249,10 @@
   more <code><a href="#the-option-element">option</a></code> elements being changed by the user, and
   before the relevant user interaction event <!-- interaction event
   spec point --> is queued (e.g. before a related <span title="event-click">click</span> event), 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-select-element">select</a></code>
-  element, using the <a href="#user-interaction-task-source">user interaction task source</a> as the
-  task source, then <a href="#broadcast-formchange-events">broadcast <code title="event-formchange">formchange</code> events</a> at the
+  <a href="#queue-a-task">queue a task</a> to <a href="#fire-a-simple-event">fire a simple event</a> tgat
+  bubbles called <code title="event-change">change</code> at the
+  <code><a href="#the-select-element">select</a></code> element, using the <a href="#user-interaction-task-source">user interaction task
+  source</a> as the task source, then <a href="#broadcast-formchange-events">broadcast <code title="event-formchange">formchange</code> events</a> at the
   element's <a href="#form-owner">form owner</a>.</p>
 
   <p>The <a href="#concept-form-reset-control" title="concept-form-reset-control">reset
@@ -30780,8 +30781,8 @@
   <p>When a <code><a href="#the-textarea-element">textarea</a></code> is <a href="#concept-textarea-mutable" title="concept-textarea-mutable">mutable</a>, its <a href="#concept-textarea-raw-value" title="concept-textarea-raw-value">raw value</a> should be
   editable by the user. Any time the user causes the element's <a href="#concept-textarea-raw-value" title="concept-textarea-raw-value">raw 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-textarea-element">textarea</a></code> element, then <a href="#broadcast-forminput-events">broadcast <code title="event-forminput">forminput</code> events</a> at the
+  event</a> that bubbls called <code title="event-input">input</code> at the <code><a href="#the-textarea-element">textarea</a></code>
+  element, then <a href="#broadcast-forminput-events">broadcast <code title="event-forminput">forminput</code> events</a> at the
   <code><a href="#the-textarea-element">textarea</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
@@ -48525,14 +48526,13 @@
    element, and the element does not have a defined <a href="#activation-behavior">activation
    behavior</a>, and the user has changed the element's <a href="#concept-fe-value" title="concept-fe-value">value</a> or its list of <a href="#concept-input-type-file-selected" title="concept-input-type-file-selected">selected files</a>
    while the control was focused without committing that change, then
-   <a href="#fire-a-simple-event">fire a simple event</a> called <code title="event-change">change</code> at the element, then
+   <a href="#fire-a-simple-event">fire a simple event</a> that bubbles called <code title="event-change">change</code> at the element, then
    <a href="#broadcast-formchange-events">broadcast <code title="event-formchange">formchange</code>
    events</a> at the element's <a href="#form-owner">form owner</a>.</p>
 
    <li><p>Unfocus the element.</li>
 
-   <li><p><a href="#fire-a-simple-event">Fire a simple event</a> that doesn't bubble called
-   <code title="event-blur">blur</code> at the element.</li>
+   <li><p><a href="#fire-a-simple-event">Fire a simple event</a> called <code title="event-blur">blur</code> at the element.</li>
 
   </ol><p>When an element that is focused stops being a
   <a href="#focusable">focusable</a> element, or stops being focused without
Received on Monday, 27 July 2009 23:11:25 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 July 2009 23:11:27 GMT