[html5] r8401 - [giow] (2) Define that text fields fire 'select' events when selection changes F [...]
whatwg at whatwg.org
whatwg at whatwg.org
Thu Jan 16 10:40:39 PST 2014
Author: ianh
Date: 2014-01-16 10:40:38 -0800 (Thu, 16 Jan 2014)
New Revision: 8401
Modified:
complete.html
index
source
Log:
[giow] (2) Define that text fields fire 'select' events when selection changes
Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=24243
Affected topics: HTML, Rendering
Modified: complete.html
===================================================================
--- complete.html 2014-01-16 17:51:24 UTC (rev 8400)
+++ complete.html 2014-01-16 18:40:38 UTC (rev 8401)
@@ -95463,10 +95463,15 @@
or <a href="#e-mail-state-(type=email)" title=attr-input-type-email>E-mail</a> state, the element is expected to render as
an 'inline-block' box rendered as a text field.</p>
- <p>When the <i title="">input-password</i> binding applies, to an <code><a href=#the-input-element>input</a></code> element whose
+ <p>When the <i title="">input-password</i> binding applies to an <code><a href=#the-input-element>input</a></code> element whose
<code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute is in the <a href="#password-state-(type=password)" title=attr-input-type-password>Password</a> state, the element is expected to render as an
'inline-block' box rendered as a text field whose contents are obscured.</p>
+ <p>If these text fields provide a text selection, then, when the user changes the currect
+ selection in such a binding, the user agent is expected to <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire
+ a simple event</a> that bubbles named <code title=event-select><a href=#event-select>select</a></code> at the element,
+ using the <a href=#user-interaction-task-source>user interaction task source</a> as the task source.</p>
+
<p>If an <code><a href=#the-input-element>input</a></code> element whose <code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute is
in one of the above states has a <code title=attr-input-size><a href=#attr-input-size>size</a></code> attribute, and parsing
that attribute's value using the <a href=#rules-for-parsing-non-negative-integers>rules for parsing non-negative integers</a> doesn't
@@ -95906,7 +95911,11 @@
textarea { binding: <i title="">textarea</i>; white-space: pre-wrap; }</pre>
<p>When the <i title="">textarea</i> binding applies to a <code><a href=#the-textarea-element>textarea</a></code> element, the
- element is expected to render as an 'inline-block' box rendered as a multiline text field.</p>
+ element is expected to render as an 'inline-block' box rendered as a multiline text field. If this
+ text field provides a selection, then, when the user changes the currect selection in such a
+ binding, the user agent is expected to <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple
+ event</a> that bubbles named <code title=event-select><a href=#event-select>select</a></code> at the element, using
+ the <a href=#user-interaction-task-source>user interaction task source</a> as the task source.</p>
<p>If the element has a <code title=attr-textarea-cols><a href=#attr-textarea-cols>cols</a></code> attribute, and parsing that
attribute's value using the <a href=#rules-for-parsing-non-negative-integers>rules for parsing non-negative integers</a> doesn't generate
@@ -102027,7 +102036,7 @@
<tr><!-- select --><td> <dfn id=event-select title=event-select><code>select</code></dfn>
<td> <code><a href=#event>Event</a></code>
<td> Form controls
- <td> Fired at form controls when an API adjusts the text selection
+ <td> Fired at form controls when their text selection is adjusted (whether by an API or by the user)
<tr><!-- show --><td> <dfn id=event-show title=event-show><code>show</code></dfn>
<td> <code><a href=#relatedevent>RelatedEvent</a></code>
Modified: index
===================================================================
--- index 2014-01-16 17:51:24 UTC (rev 8400)
+++ index 2014-01-16 18:40:38 UTC (rev 8401)
@@ -95463,10 +95463,15 @@
or <a href="#e-mail-state-(type=email)" title=attr-input-type-email>E-mail</a> state, the element is expected to render as
an 'inline-block' box rendered as a text field.</p>
- <p>When the <i title="">input-password</i> binding applies, to an <code><a href=#the-input-element>input</a></code> element whose
+ <p>When the <i title="">input-password</i> binding applies to an <code><a href=#the-input-element>input</a></code> element whose
<code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute is in the <a href="#password-state-(type=password)" title=attr-input-type-password>Password</a> state, the element is expected to render as an
'inline-block' box rendered as a text field whose contents are obscured.</p>
+ <p>If these text fields provide a text selection, then, when the user changes the currect
+ selection in such a binding, the user agent is expected to <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire
+ a simple event</a> that bubbles named <code title=event-select><a href=#event-select>select</a></code> at the element,
+ using the <a href=#user-interaction-task-source>user interaction task source</a> as the task source.</p>
+
<p>If an <code><a href=#the-input-element>input</a></code> element whose <code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute is
in one of the above states has a <code title=attr-input-size><a href=#attr-input-size>size</a></code> attribute, and parsing
that attribute's value using the <a href=#rules-for-parsing-non-negative-integers>rules for parsing non-negative integers</a> doesn't
@@ -95906,7 +95911,11 @@
textarea { binding: <i title="">textarea</i>; white-space: pre-wrap; }</pre>
<p>When the <i title="">textarea</i> binding applies to a <code><a href=#the-textarea-element>textarea</a></code> element, the
- element is expected to render as an 'inline-block' box rendered as a multiline text field.</p>
+ element is expected to render as an 'inline-block' box rendered as a multiline text field. If this
+ text field provides a selection, then, when the user changes the currect selection in such a
+ binding, the user agent is expected to <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple
+ event</a> that bubbles named <code title=event-select><a href=#event-select>select</a></code> at the element, using
+ the <a href=#user-interaction-task-source>user interaction task source</a> as the task source.</p>
<p>If the element has a <code title=attr-textarea-cols><a href=#attr-textarea-cols>cols</a></code> attribute, and parsing that
attribute's value using the <a href=#rules-for-parsing-non-negative-integers>rules for parsing non-negative integers</a> doesn't generate
@@ -102027,7 +102036,7 @@
<tr><!-- select --><td> <dfn id=event-select title=event-select><code>select</code></dfn>
<td> <code><a href=#event>Event</a></code>
<td> Form controls
- <td> Fired at form controls when an API adjusts the text selection
+ <td> Fired at form controls when their text selection is adjusted (whether by an API or by the user)
<tr><!-- show --><td> <dfn id=event-show title=event-show><code>show</code></dfn>
<td> <code><a href=#relatedevent>RelatedEvent</a></code>
Modified: source
===================================================================
--- source 2014-01-16 17:51:24 UTC (rev 8400)
+++ source 2014-01-16 18:40:38 UTC (rev 8401)
@@ -106233,11 +106233,16 @@
or <span data-x="attr-input-type-email">E-mail</span> state, the element is expected to render as
an 'inline-block' box rendered as a text field.</p>
- <p>When the <i data-x="">input-password</i> binding applies, to an <code>input</code> element whose
+ <p>When the <i data-x="">input-password</i> binding applies to an <code>input</code> element whose
<code data-x="attr-input-type">type</code> attribute is in the <span
data-x="attr-input-type-password">Password</span> state, the element is expected to render as an
'inline-block' box rendered as a text field whose contents are obscured.</p>
+ <p>If these text fields provide a text selection, then, when the user changes the currect
+ selection in such a binding, the user agent is expected to <span>queue a task</span> to <span>fire
+ a simple event</span> that bubbles named <code data-x="event-select">select</code> at the element,
+ using the <span>user interaction task source</span> as the task source.</p>
+
<p>If an <code>input</code> element whose <code data-x="attr-input-type">type</code> attribute is
in one of the above states has a <code data-x="attr-input-size">size</code> attribute, and parsing
that attribute's value using the <span>rules for parsing non-negative integers</span> doesn't
@@ -106723,7 +106728,11 @@
textarea { binding: <i data-x="">textarea</i>; white-space: pre-wrap; }</pre>
<p>When the <i data-x="">textarea</i> binding applies to a <code>textarea</code> element, the
- element is expected to render as an 'inline-block' box rendered as a multiline text field.</p>
+ element is expected to render as an 'inline-block' box rendered as a multiline text field. If this
+ text field provides a selection, then, when the user changes the currect selection in such a
+ binding, the user agent is expected to <span>queue a task</span> to <span>fire a simple
+ event</span> that bubbles named <code data-x="event-select">select</code> at the element, using
+ the <span>user interaction task source</span> as the task source.</p>
<p>If the element has a <code data-x="attr-textarea-cols">cols</code> attribute, and parsing that
attribute's value using the <span>rules for parsing non-negative integers</span> doesn't generate
@@ -113857,7 +113866,7 @@
<td> <dfn data-x="event-select"><code>select</code></dfn>
<td> <code>Event</code>
<td> Form controls
- <td> Fired at form controls when an API adjusts the text selection
+ <td> Fired at form controls when their text selection is adjusted (whether by an API or by the user)
<tr> <!-- show -->
<td> <dfn data-x="event-show"><code>show</code></dfn>
More information about the Commit-Watchers
mailing list