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. (whatwg r3257)

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. (whatwg
r3257)

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.2404&r2=1.2405&f=h
http://html5.org/tools/web-apps-tracker?from=3256&to=3257

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2404
retrieving revision 1.2405
diff -u -d -r1.2404 -r1.2405
--- Overview.html 15 Jun 2009 19:45:38 -0000 1.2404
+++ Overview.html 15 Jun 2009 20:01:58 -0000 1.2405
@@ -6186,7 +6186,7 @@
    return no nodes; none of the elements above are in the "aaa,bbb"
    class.</p>
 
-  </div><!-- XXX
+  </div><!-- v2:
 >         * xGetParentElementByClassName(rootElement, className, tagName) -
 > Navigates upwards until we hit a parent element with the given class name and
 > optional tag name.
@@ -7099,8 +7099,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
@@ -7138,10 +7138,7 @@
    <li>
 
     <p>Dispatching the required <code title="event-click">click</code>
-    event.</p>
-
-    <p class="XXX">Another specification presumably requires the
-    firing of the <span title="event-click">click</span> event?</p>
+    event.</p> <!-- interaction event spec point -->
 
     <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
@@ -29127,9 +29124,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
@@ -29163,12 +29161,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
@@ -47538,10 +47536,6 @@
   and submit respectively. Only their presentation to the user
   changes.<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>
@@ -49301,7 +49295,7 @@
   set to the view with which the user interacted to trigger the
   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><table><thead><tr><th> Event Name </th>
+  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>
      <th> Bubbles? </th>
      <th> Cancelable? </th>

Received on Monday, 15 June 2009 20:02:48 UTC