- From: poot <cvsmail@w3.org>
- Date: Mon, 15 Jun 2009 09:42:55 +0900 (JST)
- To: public-html-diffs@w3.org
v2 notes for dnd (whatwg r3249) http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.2396&r2=1.2397&f=h http://html5.org/tools/web-apps-tracker?from=3248&to=3249 =================================================================== RCS file: /sources/public/html5/spec/Overview.html,v retrieving revision 1.2396 retrieving revision 1.2397 diff -u -d -r1.2396 -r1.2397 --- Overview.html 15 Jun 2009 00:36:21 -0000 1.2396 +++ Overview.html 15 Jun 2009 00:42:40 -0000 1.2397 @@ -49005,31 +49005,43 @@ </div> - </div><h3 id="dnd"><span class="secno">7.10 </span><dfn>Drag and drop</dfn></h3><!--XXX + </div><h3 id="dnd"><span class="secno">7.10 </span><dfn>Drag and drop</dfn></h3><!-- v2 ideas for drag and drop: -http://msdn.microsoft.com/workshop/author/datatransfer/overview.asp -http://msdn.microsoft.com/workshop/author/dhtml/reference/objects/clipboarddata.asp + * being able to animate a drop target: -> To implement this with simple interface I've proposed, events should be -> handled either by existing elements (like list items that compare their size -> and position of dragged element to decide whether element should be dropped -> before or after) or handled by container that would probably need to calculate -> positions of it's children and create new element to show drop target. Smooth -> Mac-like drag'n'drop can be implemented by animating drop target's -> padding/margin. So that's quite a bit of code that's going to be reinvented -> each time someone implements reordering. + > To implement this with simple interface I've proposed, events + > should be handled either by existing elements (like list + > items that compare their size and position of dragged element + > to decide whether element should be dropped before or after) + > or handled by container that would probably need to calculate + > positions of it's children and create new element to show + > drop target. Smooth Mac-like drag'n'drop can be implemented + > by animating drop target's padding/margin. So that's quite a + > bit of code that's going to be reinvented each time someone + > implements reordering. -<hyatt> :droptarget -<hyatt> or something -<hyatt> we don't support a pseudo-class for the drop target but that's a great idea -<Hixie_> yeah, thinking about that too -<Hixie_> :drop-target, :drop-target(above), :drop-target(below) and having ondragover be able to say "not on me, but next to me maybe" + <hyatt> :droptarget + <hyatt> or something + <hyatt> we don't support a pseudo-class for the drop target but that's a great idea + <Hixie_> yeah, thinking about that too + <Hixie_> :drop-target, :drop-target(above), :drop-target(below) and having ondragover be able to say "not on me, but next to me maybe" + + * We should let drop targets communicate back to drag sources if + they want to communicate. (e.g. expose Window, and thus + postMessage(), on the dataTransfer object on drop.) + + We should let drag sources provide a set of options via a + context menu when the drop happens. (So that, e.g., the source + can know whether a capabilities URI that it is passing along is + supposed to be read-write access or read-only access to the + object being dragged.) + + We should let potential drop targets see the types (but not the + contents!) of dragged data so they can establish if they care + or not. (dataTransfer.hasType()) + + Ack: Ben Laurie (@g) -http://msdn.microsoft.com/workshop/author/dhtml/reference/events/ondragstart.asp -http://msdn.microsoft.com/workshop/author/dhtml/reference/events/ondrag.asp -http://msdn.microsoft.com/workshop/author/dhtml/reference/events/ondragend.asp -http://msdn.microsoft.com/workshop/author/dhtml/reference/objects/obj_datatransfer.asp -http://developer.apple.com/documentation/AppleApplications/Conceptual/SafariJSProgTopics/Tasks/DragAndDrop.html --><p>This section defines an event-based drag-and-drop mechanism.<p>This specification does not define exactly what a <em>drag-and-drop operation</em> actually is.<p>On a visual medium with a pointing device, a drag operation could be the default action of a <code title="event-mousedown">mousedown</code> event that is followed by a
Received on Monday, 15 June 2009 00:43:28 UTC