[html5] r3588 - [] (0) Clarify DragEvent's MouseEvent attributes are set to 0 when there's no mo [...]
whatwg at whatwg.org
whatwg at whatwg.org
Tue Aug 11 15:23:51 PDT 2009
Author: ianh
Date: 2009-08-11 15:23:50 -0700 (Tue, 11 Aug 2009)
New Revision: 3588
Modified:
index
source
Log:
[] (0) Clarify DragEvent's MouseEvent attributes are set to 0 when there's no mouse interaction going on.
Modified: index
===================================================================
--- index 2009-08-11 07:25:34 UTC (rev 3587)
+++ index 2009-08-11 22:23:50 UTC (rev 3588)
@@ -59739,7 +59739,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);
@@ -60002,7 +60002,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
@@ -60011,9 +60015,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>
Modified: source
===================================================================
--- source 2009-08-11 07:25:34 UTC (rev 3587)
+++ source 2009-08-11 22:23:50 UTC (rev 3588)
@@ -65445,7 +65445,7 @@
<p>The drag-and-drop processing model involves several events. They
all use the <code>DragEvent</code> interface.</p>
- <pre class="idl">interface <dfn>DragEvent</dfn> : MouseEvent {
+ <pre class="idl">interface <dfn>DragEvent</dfn> : <span>MouseEvent</span> {
readonly attribute <span>DataTransfer</span> <span title="dom-DragEvent-dataTransfer">dataTransfer</span>;
void <span title="dom-DragEvent-initDragEvent">initDragEvent</span>(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 <span>DataTransfer</span> dataTransferArg);
@@ -65755,7 +65755,11 @@
<h4>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>DragEvent</code> interface defined above, must have
the bubbling and cancelable behaviors given in the table below, and
@@ -65766,9 +65770,17 @@
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>
+ 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>
More information about the Commit-Watchers
mailing list