W3C home > Mailing lists > Public > public-html-commits@w3.org > December 2008

html5/spec Overview.html,1.1690,1.1691

From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 02 Dec 2008 10:40:52 +0000
To: public-html-commits@w3.org
Message-Id: <E1L7SgW-0007We-GA@lionel-hutz.w3.org>

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

Modified Files:
	Overview.html 
Log Message:
WF2: Fire 'input' for <textarea> too. (whatwg r2520)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.1690
retrieving revision 1.1691
diff -u -d -r1.1690 -r1.1691
--- Overview.html	2 Dec 2008 10:18:40 -0000	1.1690
+++ Overview.html	2 Dec 2008 10:40:49 -0000	1.1691
@@ -22039,12 +22039,13 @@
   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 class=example>Examples of a user changing the element's <a href=#concept-fe-value title=concept-fe-value>value</a> would include the user typing
+  the user pauses, instead of continuously for each keystroke.</p><!-- same text is present in the <textarea> section --><p class=example>Examples of a user changing the element's <a href=#concept-fe-value title=concept-fe-value>value</a> would include the user typing
   into a text field, pasting a new value into the field, or undoing an
   edit in that field. Some user interactions do not cause changes to
   the value, e.g. hitting the "delete" key in an empty text field, or
   replacing some text in the field with text from the clipboard that
-  happens to be exactly the same text.<p>When the <dfn id=event-input-change title=event-input-change><code>change</code></dfn> event applies,
+  happens to be exactly the same text.</p><!-- XXX consider putting the above example in a section that
+  applies to "input" events for the <textarea> element too --><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 any time the user commits a change to the element's
@@ -22587,7 +22588,15 @@
   <a href=#barred-from-constraint-validation>barred from constraint validation</a>.<p>A <code><a href=#the-textarea-element>textarea</a></code> element is <dfn id=concept-textarea-mutable title=concept-textarea-mutable>mutable</dfn> if it is neither
   <a href=#concept-fe-disabled title=concept-fe-disabled>disabled</a> nor has a <code title=attr-textarea-readonly><a href=#attr-textarea-readonly>readonly</a></code> attribute
   specified.<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.<p>A <code><a href=#the-textarea-element>textarea</a></code> element has a <dfn id=concept-textarea-dirty title=concept-textarea-dirty>dirty value flag</dfn>, which must 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
+  <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
+  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><!-- same text is present in the <input> section --><p>A <code><a href=#the-textarea-element>textarea</a></code> element has a <dfn id=concept-textarea-dirty title=concept-textarea-dirty>dirty value flag</dfn>, which must be
   initially set to false, and must be set to true whenever the user
   interacts with the control in a way that changes the <a href=#concept-textarea-raw-value title=concept-textarea-raw-value>raw value</a>.<p>When the <code><a href=#the-textarea-element>textarea</a></code> element's <code><a href=#textcontent>textContent</a></code>
   DOM attribute changes value, if the element's <a href=#concept-textarea-dirty title=concept-textarea-dirty>dirty value flag</a> is false,
Received on Tuesday, 2 December 2008 10:41:01 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 December 2008 10:41:01 GMT