hixie: Clarify DragEvent's MouseEvent attributes are set to 0 when there's no mouse interaction going on. (whatwg r3588)

hixie: Clarify DragEvent's MouseEvent attributes are set to 0 when
there's no mouse interaction going on. (whatwg r3588)

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.2780&r2=1.2781&f=h
http://html5.org/tools/web-apps-tracker?from=3587&to=3588

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2780
retrieving revision 1.2781
diff -u -d -r1.2780 -r1.2781
--- Overview.html 11 Aug 2009 07:25:39 -0000 1.2780
+++ Overview.html 11 Aug 2009 22:23:56 -0000 1.2781
@@ -59951,7 +59951,7 @@
   <p>The drag-and-drop processing model involves several events. They
   all use the <code><a href="#dragevent">DragEvent</a></code> interface.</p>
 
-  <pre class="idl">interface <dfn id="dragevent">DragEvent</dfn> : MouseEvent {
+  <pre class="idl">interface <dfn id="dragevent">DragEvent</dfn> : <span>MouseEvent</span> {
   readonly attribute <a href="#datatransfer">DataTransfer</a> <a href="#dom-dragevent-datatransfer" title="dom-DragEvent-dataTransfer">dataTransfer</a>;
 
   void <a href="#dom-dragevent-initdragevent" title="dom-DragEvent-initDragEvent">initDragEvent</a>(in DOMString typeArg, in boolean canBubbleArg, in boolean cancelableArg, in <span>AbstractView</span> viewArg, in long detailArg, in long screenXArg, in long screenYArg, in long clientXArg, in long clientYArg, in boolean ctrlKeyArg, in boolean altKeyArg, in boolean shiftKeyArg, in boolean metaKeyArg, in unsigned short buttonArg, in EventTarget relatedTargetArg, in <a href="#datatransfer">DataTransfer</a> dataTransferArg);
@@ -60214,7 +60214,11 @@
   <h4 id="events-fired-during-a-drag-and-drop-action"><span class="secno">7.10.3 </span>Events fired during a drag-and-drop action</h4>
 
   <p>The following events are involved in the drag-and-drop
-  model. <span class="impl">Whenever the processing model described
+  model.</p>
+
+  <div class="impl">
+
+  <p>Whenever the processing model described
   below causes one of these events to be fired, the event fired must
   use the <code><a href="#dragevent">DragEvent</a></code> interface defined above, must have
   the bubbling and cancelable behaviors given in the table below, and
@@ -60223,9 +60227,15 @@
   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></p>
+  devices as they would be for user interaction events, and the <code title="">relatedTarget</code> attribute set to null.</p>
+
+  <p>If there is no relevant pointing device, the object must have its
+  <code title="">screenX</code>, <code title="">screenY</code>, <code title="">clientX</code>, <code title="">clientY</code>, and <code title="">button</code> attributes set to 0.</p>
+
   <!-- interaction event spec point -->
 
+  </div>
+
   <table>
 
    <thead>

Received on Tuesday, 11 August 2009 22:24:56 UTC