[html5] r977 - /

[whatwg at whatwg.org]

Author: ianh
Date: 2007-08-06 17:47:00 -0700 (Mon, 06 Aug 2007)
New Revision: 977

Modified:
   index
   source
Log:
[iw] (2) Make the DragEvents be UIEvents instead of regular Events (not that this has much effect on anything).

Modified: index
===================================================================
--- index	2007-08-06 21:29:33 UTC (rev 976)
+++ index	2007-08-07 00:47:00 UTC (rev 977)
@@ -22,7 +22,7 @@
 
    <h1 id=html-5>HTML 5</h1>
 
-   <h2 class="no-num no-toc" id=working>Working Draft — 6 August 2007</h2>
+   <h2 class="no-num no-toc" id=working>Working Draft — 7 August 2007</h2>
 
    <p>You can take part in this work. <a
     href="http://www.whatwg.org/mailing-list">Join the working group's
@@ -28809,10 +28809,10 @@
   <p>The drag-and-drop processing model involves several events. They all use
    the <code><a href="#dragevent">DragEvent</a></code> interface.
 
-  <pre class=idl>interface <dfn id=dragevent>DragEvent</dfn> : Event {
+  <pre class=idl>interface <dfn id=dragevent>DragEvent</dfn> : UIEvent {
   readonly attribute <a href="#datatransfer0">DataTransfer</a> <a href="#datatransfer" title=dom-DragEvent-dataTransfer>dataTransfer</a>;
-  void <a href="#initdragevent" title=dom-DragEvent-initDragEvent>initDragEvent</a>(in DOMString typeArg, in boolean canBubbleArg, in boolean cancelableArg);
-  void <a href="#initdrageventns" title=dom-DragEvent-initDragEventNS>initDragEventNS</a>(in DOMString namespaceURIArg, in DOMString typeArg, in boolean canBubbleArg, in boolean cancelableArg);
+  void <a href="#initdragevent" title=dom-DragEvent-initDragEvent>initDragEvent</a>(in DOMString typeArg, in boolean canBubbleArg, in boolean cancelableArg, in AbstractView viewArg, in long detailArg, in <a href="#datatransfer0">DataTransfer</a> dataTransferArg);
+  void <a href="#initdrageventns" title=dom-DragEvent-initDragEventNS>initDragEventNS</a>(in DOMString namespaceURIArg, in DOMString typeArg, in boolean canBubbleArg, in boolean cancelableArg, in AbstractView viewArg, in long detailArg, in <a href="#datatransfer0">DataTransfer</a> dataTransferArg);
 };</pre>
 
   <p>The <dfn id=initdragevent
@@ -28960,7 +28960,10 @@
    fired, the event fired must use the <code><a
    href="#dragevent">DragEvent</a></code> interface defined above, must have
    the bubbling and cancelable behaviours given in the table below, and must
-   have the context information set up as described after the table.
+   have the context information set up as described after the table, with the
+   <code title=dom-UIEvent-view>view</code> attribute set to the view with
+   which the user interacted to trigger the drag-and-drop event, and the
+   <code title=dom-UIEvent-detail>detail</code> attribute set to zero.
 
   <table>
    <thead>
@@ -29643,7 +29646,10 @@
   <p>The model described above is independent of which <code>Document</code>
    object the nodes involved are from; the events must be fired as described
    above and the rest of the processing model must be followed as described
-   above, irrespective of how many documents are involved in the operation.
+   above, irrespective of how many documents are involved in the operation.</p>
+  <!-- should we mention that you shouldn't include the view from the
+  source in the events to the target, or is that obvious enough from
+  the requirements in the event section above? -->
 
   <h5 id=when-the0><span class=secno>5.3.3.2. </span>When the drag-and-drop
    operation starts or ends in another application</h5>

Modified: source
===================================================================
--- source	2007-08-06 21:29:33 UTC (rev 976)
+++ source	2007-08-07 00:47:00 UTC (rev 977)
@@ -26278,10 +26278,10 @@
   <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> : Event {
+  <pre class="idl">interface <dfn>DragEvent</dfn> : UIEvent {
   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);
-  void <span title="dom-DragEvent-initDragEventNS">initDragEventNS</span>(in DOMString namespaceURIArg, in DOMString typeArg, in boolean canBubbleArg, in boolean cancelableArg);
+  void <span title="dom-DragEvent-initDragEvent">initDragEvent</span>(in DOMString typeArg, in boolean canBubbleArg, in boolean cancelableArg, in AbstractView viewArg, in long detailArg, in <span>DataTransfer</span> dataTransferArg);
+  void <span title="dom-DragEvent-initDragEventNS">initDragEventNS</span>(in DOMString namespaceURIArg, in DOMString typeArg, in boolean canBubbleArg, in boolean cancelableArg, in AbstractView viewArg, in long detailArg, in <span>DataTransfer</span> dataTransferArg);
 };</pre>
 
   <p>The <dfn
@@ -26430,7 +26430,10 @@
   <code>DragEvent</code> interface defined above, must have the
   bubbling and cancelable behaviours given in the table below, and
   must have the context information set up as described after the
-  table.</p>
+  table, with the <code title="dom-UIEvent-view">view</code> attribute
+  set to the view with which the user interacted to trigger the
+  drag-and-drop event, and the <code
+  title="dom-UIEvent-detail">detail</code> attribute set to zero.</p>
 
   <table>
 
@@ -27071,7 +27074,11 @@
   model must be followed as described above, irrespective of how many
   documents are involved in the operation.</p>
 
+  <!-- should we mention that you shouldn't include the view from the
+  source in the events to the target, or is that obvious enough from
+  the requirements in the event section above? -->
 
+
   <h5>When the drag-and-drop operation starts or ends in another
   application</h5>