[html5] r3257 - [e] (0) mark the points where we are implying the existence of an Interaction Ev [...]
whatwg at whatwg.org
whatwg at whatwg.org
Mon Jun 15 13:01:55 PDT 2009
Author: ianh
Date: 2009-06-15 13:01:53 -0700 (Mon, 15 Jun 2009)
New Revision: 3257
Modified:
index
source
Log:
[e] (0) mark the points where we are implying the existence of an Interaction Events spec, so that once it exists we can do the cross-refs.
Modified: index
===================================================================
--- index 2009-06-15 19:45:33 UTC (rev 3256)
+++ index 2009-06-15 20:01:53 UTC (rev 3257)
@@ -6889,7 +6889,7 @@
</div>
-<!-- XXX
+<!-- v2:
> * xGetParentElementByClassName(rootElement, className, tagName) -
> Navigates upwards until we hit a parent element with the given class name and
> optional tag name.
@@ -8071,8 +8071,8 @@
keyboard or voice input, or through mouse clicks. When the user
triggers an element with a defined <a href=#activation-behavior>activation behavior</a>
in a manner other than clicking it, the default action of the
- interaction event<!-- XXX --> must be to <a href=#run-synthetic-click-activation-steps>run synthetic click
- activation steps</a> on the element.</p>
+ interaction event must be to <a href=#run-synthetic-click-activation-steps>run synthetic click activation
+ steps</a> on the element.</p> <!-- interaction event spec point -->
<p>When a user agent is to <dfn id=run-synthetic-click-activation-steps>run synthetic click activation
steps</dfn> on an element, the user agent must <a href=#run-pre-click-activation-steps>run pre-click
@@ -8110,11 +8110,8 @@
<li>
<p>Dispatching the required <code title=event-click>click</code>
- event.</p>
+ event.</p> <!-- interaction event spec point -->
- <p class=XXX>Another specification presumably requires the
- firing of the <span title=event-click>click</span> event?</p>
-
<p>If there is an element <var title="">e</var>, then the default
action of the <span title=event-click>click</span> event must be
to <a href=#run-post-click-activation-steps>run post-click activation steps</a> on element <var title="">e</var>.</p>
@@ -32957,9 +32954,10 @@
<code><a href=#the-option-element>option</a></code> element being <dfn id=concept-select-pick title=concept-select-pick>picked</dfn> (either through a click, or
through unfocusing the element after changing its value, or through
a <a href=#using-the-option-element-to-define-a-command title=option-command>menu command</a>, or through any
- other mechanism), and before the relevant user interaction event is
- queued (e.g. before the <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
+ other mechanism), and before the relevant user interaction event
+ <!-- interaction event spec point --> is queued (e.g. before the
+ <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>
element, using the <a href=#user-interaction-task-source>user interaction task source</a> as the
@@ -32993,12 +32991,12 @@
(either through a click, or through a <a href=#using-the-option-element-to-define-a-command title=option-command>menu command</a>, or any other
mechanism). Upon the <a href=#concept-option-selectedness title=concept-option-selectedness>selectedness</a> of one or
more <code><a href=#the-option-element>option</a></code> elements being changed by the user, and
- before the relevant user interaction event 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
+ 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
element's <a href=#form-owner>form owner</a>.</p>
<p>The <a href=#concept-form-reset-control title=concept-form-reset-control>reset
@@ -53069,10 +53067,6 @@
<div class=impl>
- <!-- XXX might be worth disabling user interaction event submission
- in hidden areas? e.g. make onmousemove and onclick and form controls
- not respond to input? -->
-
<p>The <dfn id=dom-hidden title=dom-hidden><code>hidden</code></dfn> DOM
attribute must <a href=#reflect>reflect</a> the content attribute of the
same name.</p>
@@ -55039,6 +55033,7 @@
drag-and-drop event, the <code title=dom-UIEvent-detail>detail</code> attribute set to zero, the
mouse and key attributes set according to the state of the input
devices as they would be for user interaction events, and the <code title="">relatedTarget</code> attribute set to null.</span></p>
+ <!-- interaction event spec point -->
<table><thead><tr><th> Event Name </th>
<th> Target </th>
Modified: source
===================================================================
--- source 2009-06-15 19:45:33 UTC (rev 3256)
+++ source 2009-06-15 20:01:53 UTC (rev 3257)
@@ -6871,7 +6871,7 @@
</div>
-<!-- XXX
+<!-- v2:
> * xGetParentElementByClassName(rootElement, className, tagName) -
> Navigates upwards until we hit a parent element with the given class name and
> optional tag name.
@@ -8173,8 +8173,8 @@
keyboard or voice input, or through mouse clicks. When the user
triggers an element with a defined <span>activation behavior</span>
in a manner other than clicking it, the default action of the
- interaction event<!-- XXX --> must be to <span>run synthetic click
- activation steps</span> on the element.</p>
+ interaction event must be to <span>run synthetic click activation
+ steps</span> on the element.</p> <!-- interaction event spec point -->
<p>When a user agent is to <dfn>run synthetic click activation
steps</dfn> on an element, the user agent must <span>run pre-click
@@ -8219,11 +8219,8 @@
<li>
<p>Dispatching the required <code title="event-click">click</code>
- event.</p>
+ event.</p> <!-- interaction event spec point -->
- <p class="XXX">Another specification presumably requires the
- firing of the <span title="event-click">click</span> event?</p>
-
<p>If there is an element <var title="">e</var>, then the default
action of the <span title="event-click">click</span> event must be
to <span>run post-click activation steps</span> on element <var
@@ -36707,9 +36704,10 @@
title="concept-select-pick">picked</dfn> (either through a click, or
through unfocusing the element after changing its value, or through
a <span title="option-command">menu command</span>, or through any
- other mechanism), and before the relevant user interaction event is
- queued (e.g. before the <span title="event-click">click</span>
- event), the user agent must set the <span
+ other mechanism), and before the relevant user interaction event
+ <!-- interaction event spec point --> is queued (e.g. before the
+ <span title="event-click">click</span> event), the user agent must
+ set the <span
title="concept-option-selectedness">selectedness</span> of the
picked <code>option</code> element to true and then <span>queue a
task</span> to <span>fire a simple event</span> called <code
@@ -36761,12 +36759,13 @@
mechanism). Upon the <span
title="concept-option-selectedness">selectedness</span> of one or
more <code>option</code> elements being changed by the user, and
- before the relevant user interaction event is queued (e.g. before a
- related <span title="event-click">click</span> event), the user
- agent must <span>queue a task</span> to <span>fire a simple
- event</span> called <code title="event-change">change</code> at the
- <code>select</code> element, using the <span>user interaction task
- source</span> as the task source, then <span>broadcast <code
+ 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
+ <span>queue a task</span> to <span>fire a simple event</span> called
+ <code title="event-change">change</code> at the <code>select</code>
+ element, using the <span>user interaction task source</span> as the
+ task source, then <span>broadcast <code
title="event-formchange">formchange</code> events</span> at the
element's <span>form owner</span>.</p>
@@ -62177,10 +62176,6 @@
<div class="impl">
- <!-- XXX might be worth disabling user interaction event submission
- in hidden areas? e.g. make onmousemove and onclick and form controls
- not respond to input? -->
-
<p>The <dfn title="dom-hidden"><code>hidden</code></dfn> DOM
attribute must <span>reflect</span> the content attribute of the
same name.</p>
@@ -64458,6 +64453,7 @@
mouse and key attributes set according to the state of the input
devices as they would be for user interaction events, and the <code
title="">relatedTarget</code> attribute set to null.</span></p>
+ <!-- interaction event spec point -->
<table>
More information about the Commit-Watchers
mailing list