Skip to content

Commit

Permalink
[giow] (2) Spec the 'select' event.
Browse files Browse the repository at this point in the history
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=12132

git-svn-id: http://svn.whatwg.org/webapps@6070 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed May 4, 2011
1 parent 6e3b78b commit 7ccc3c5
Show file tree
Hide file tree
Showing 3 changed files with 41 additions and 6 deletions.
15 changes: 13 additions & 2 deletions complete.html
Expand Up @@ -50092,6 +50092,12 @@ <h4 id=textFieldSelection><span class=secno>4.10.20 </span>APIs for the text fie
elements, these methods and attributes must operate on the element's
<a href=#concept-textarea-raw-value title=concept-textarea-raw-value>raw value</a>.</p>

<p>Where possible, user interface features for changing the text
selection in <code><a href=#the-input-element>input</a></code> and <code><a href=#the-textarea-element>textarea</a></code> elements
must be implemented in terms of the DOM API described in this
section, so that, e.g., all the same events fire.</p>


<p>The selections of <code><a href=#the-input-element>input</a></code> and <code><a href=#the-textarea-element>textarea</a></code>
elements have a <i>direction</i>, which is either <i>forward</i>,
<i>backward</i>, or <i>none</i>. This direction is set when the user
Expand All @@ -50117,7 +50123,9 @@ <h4 id=textFieldSelection><span class=secno>4.10.20 </span>APIs for the text fie
must cause the contents of the text field to be fully selected, with
the selection direction being none, if the platform support
selections with the direction <i>none</i>, or otherwise
<i>forward</i>.</p>
<i>forward</i>. The user agent must then <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>select</code> at the element, using the
<a href=#user-interaction-task-source>user interaction task source</a> as the task source.</p>


<p>The <dfn id=dom-textarea/input-selectionstart title=dom-textarea/input-selectionStart><code>selectionStart</code></dfn>
Expand Down Expand Up @@ -50180,7 +50188,10 @@ <h4 id=textFieldSelection><span class=secno>4.10.20 </span>APIs for the text fie
<a href=#case-sensitive>case-sensitive</a> match for the string "<code title="">backward</code>", <i>forward</i> if <var title="">direction</var> is a <a href=#case-sensitive>case-sensitive</a> match for
the string "<code title="">forward</code>" or if the platform does
not support selections with the direction <i>none</i>, and
<i>none</i> otherwise (including if the argument is omitted).</p>
<i>none</i> otherwise (including if the argument is omitted). The
user agent must then <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>select</code> at the element, using the
<a href=#user-interaction-task-source>user interaction task source</a> as the task source.</p>


<p>All elements to which this API applies have either a selection or
Expand Down
15 changes: 13 additions & 2 deletions index
Expand Up @@ -50120,6 +50120,12 @@ out of 233&thinsp;257&thinsp;824 bytes available&lt;/meter&gt;&lt;/p&gt;</pre>
elements, these methods and attributes must operate on the element's
<a href=#concept-textarea-raw-value title=concept-textarea-raw-value>raw value</a>.</p>

<p>Where possible, user interface features for changing the text
selection in <code><a href=#the-input-element>input</a></code> and <code><a href=#the-textarea-element>textarea</a></code> elements
must be implemented in terms of the DOM API described in this
section, so that, e.g., all the same events fire.</p>


<p>The selections of <code><a href=#the-input-element>input</a></code> and <code><a href=#the-textarea-element>textarea</a></code>
elements have a <i>direction</i>, which is either <i>forward</i>,
<i>backward</i>, or <i>none</i>. This direction is set when the user
Expand All @@ -50145,7 +50151,9 @@ out of 233&thinsp;257&thinsp;824 bytes available&lt;/meter&gt;&lt;/p&gt;</pre>
must cause the contents of the text field to be fully selected, with
the selection direction being none, if the platform support
selections with the direction <i>none</i>, or otherwise
<i>forward</i>.</p>
<i>forward</i>. The user agent must then <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>select</code> at the element, using the
<a href=#user-interaction-task-source>user interaction task source</a> as the task source.</p>


<p>The <dfn id=dom-textarea/input-selectionstart title=dom-textarea/input-selectionStart><code>selectionStart</code></dfn>
Expand Down Expand Up @@ -50208,7 +50216,10 @@ out of 233&thinsp;257&thinsp;824 bytes available&lt;/meter&gt;&lt;/p&gt;</pre>
<a href=#case-sensitive>case-sensitive</a> match for the string "<code title="">backward</code>", <i>forward</i> if <var title="">direction</var> is a <a href=#case-sensitive>case-sensitive</a> match for
the string "<code title="">forward</code>" or if the platform does
not support selections with the direction <i>none</i>, and
<i>none</i> otherwise (including if the argument is omitted).</p>
<i>none</i> otherwise (including if the argument is omitted). The
user agent must then <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>select</code> at the element, using the
<a href=#user-interaction-task-source>user interaction task source</a> as the task source.</p>


<p>All elements to which this API applies have either a selection or
Expand Down
17 changes: 15 additions & 2 deletions source
Expand Up @@ -56394,6 +56394,12 @@ out of 233&#x2009;257&#x2009;824 bytes available&lt;/meter>&lt;/p></pre>
elements, these methods and attributes must operate on the element's
<span title="concept-textarea-raw-value">raw value</span>.</p>

<p>Where possible, user interface features for changing the text
selection in <code>input</code> and <code>textarea</code> elements
must be implemented in terms of the DOM API described in this
section, so that, e.g., all the same events fire.</p>


<p>The selections of <code>input</code> and <code>textarea</code>
elements have a <i>direction</i>, which is either <i>forward</i>,
<i>backward</i>, or <i>none</i>. This direction is set when the user
Expand All @@ -56420,7 +56426,10 @@ out of 233&#x2009;257&#x2009;824 bytes available&lt;/meter>&lt;/p></pre>
must cause the contents of the text field to be fully selected, with
the selection direction being none, if the platform support
selections with the direction <i>none</i>, or otherwise
<i>forward</i>.</p>
<i>forward</i>. The user agent must then <span>queue a task</span>
to <span>fire a simple event</span> that bubbles named <code
title="event-select">select</code> at the element, using the
<span>user interaction task source</span> as the task source.</p>


<p>The <dfn
Expand Down Expand Up @@ -56502,7 +56511,11 @@ out of 233&#x2009;257&#x2009;824 bytes available&lt;/meter>&lt;/p></pre>
title="">direction</var> is a <span>case-sensitive</span> match for
the string "<code title="">forward</code>" or if the platform does
not support selections with the direction <i>none</i>, and
<i>none</i> otherwise (including if the argument is omitted).</p>
<i>none</i> otherwise (including if the argument is omitted). The
user agent must then <span>queue a task</span> to <span>fire a
simple event</span> that bubbles named <code
title="event-select">select</code> at the element, using the
<span>user interaction task source</span> as the task source.</p>


<p>All elements to which this API applies have either a selection or
Expand Down

0 comments on commit 7ccc3c5

Please sign in to comment.