[Webkit-unassigned] [Bug 21956] DragController needs to be made aware of async drags

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=21956


tony at chromium.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tony at chromium.org




------- Comment #5 from tony at chromium.org  2008-10-29 14:27 PDT -------
The drag operation is triggered in the browser process.  In the browser
process, it is a synchronous action.  However, we need to forward the drag
events from the browser process to the renderer process.  To the renderer,
these appear as distinct messages that do not block the renderer loop.  That
is, to the renderer, this appears async.

we do eventually call dragEnd, but it is called asynchronously compared to
dragStart.

Does that make sense?

(In reply to comment #2)
> (From update of attachment 24754 [edit])
> You can't just not call dragEnded, it will fail to reset appropriate logic.
> 
> More over this ifdef is awful, and chromium is the only platform for which it
> is "necessary" -- i have never encountered any platform on which drag and drop
> is not a synchronous action, and would actually consider this a bug in
> chromium.
> 


-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.