[Webkit-unassigned] [Bug 25690] Drop event is never fired when dragover's target element is removed even if the event was canceled by its ancestor
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Mon Feb 4 11:07:29 PST 2013
https://bugs.webkit.org/show_bug.cgi?id=25690
--- Comment #19 from Daniel Cheng <dcheng at chromium.org> 2013-02-04 11:09:34 PST ---
(In reply to comment #18)
> (In reply to comment #17)
>
> > > ondragenter should also return false.
> >
> > Not in WebKit.
>
> Really? It's required by HTML5. The standard _does not_ say that a dragenter event must be followed by a dragover event, but it does say that their default actions must be cancelled to permit a subsequent drop event.
>
> So the event sequence dragenter -> {dragleave|drop} is permitted per spec, but the drop should be generated only if the default action of dragenter event was cancelled.
I've spent a considerable amount of time trying to get the D&D event handling to follow the HTML spec (especially wrt cancelling the dragenter/dragover events), and it's rather tricky (often times, it only fails for one specific type of element).
I'll try to take a look at this in the next few weeks, but I have quite a lot of other things on my plate atm.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list