[Bug 14633] Drag source and drag destination can't coordinate behavior.

http://www.w3.org/Bugs/Public/show_bug.cgi?id=14633

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |ian@hixie.ch
         Resolution|                            |LATER
           Severity|normal                      |enhancement

--- Comment #1 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-11-01 03:24:41 UTC ---
There is already a plan to fix this: in a future version (probably early next
year) I plan to add the ability to pass a structured clone of data, including
possibly a port, through which any such communication can occur.

In the meantime, you can just create a shared worker from which you get a
unique transaction ID which is the data you add to the drag data store.


EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
satisfied with this response, please change the state of this bug to CLOSED. If
you have additional information and would like the editor to reconsider, please
reopen this bug. If you would like to escalate the issue to the full HTML
Working Group, please add the TrackerRequest keyword to this bug, and suggest
title and text for the tracker issue; or you may create a tracker issue
yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Partially Accepted
Change Description: none yet
Rationale: Marking "LATER" for now; I don't want to add new drag-and-drop
features until the browsers have mostly caught up with implementing the ones
we've added already. However, please do not hesitate to reopen this if you
notice that they have done so before I do.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Tuesday, 1 November 2011 03:24:57 UTC