Bug 26996 – dragend event triggers before drop event during Drag & Drop operations

• Component: DOM
• Status: RESOLVED FIXED

[Sebastian Markbåge]

During a HTML 5 drag and drop operation, the "dragend" event is suppose to trigger AFTER the "drop" event to allow for proper clean up. Currently the order is reversed.

It may be related to bug 24741.

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

[Daniel Bates]

I cannot reproduce this issue in the latest nightly r50918. I used a test case I wrote, currently at <https://bugzilla.mozilla.org/attachment.cgi?id=411490> to test with effectAllowed = "copy".

When I get a chance, I'll put together a test case for this issue to prevent a regression.

Can you second the confirmation that this issue has been resolved?

(In reply to comment #0)
> During a HTML 5 drag and drop operation, the "dragend" event is suppose to
> trigger AFTER the "drop" event to allow for proper clean up. Currently the
> order is reversed.
> 
> It may be related to bug 24741.
> 
> https://bugs.webkit.org/show_bug.cgi?id=24731

[Daniel Bates]

Created attachment 43268 [details]
Layout test

DRT/Manual test case for this issue.

We need to fix bug #31233 to test that the HTML5 drag-and-drop processing model is followed when there are two drop targets.

This test case ensures that we don't regress on this bug. Moreover, it ensure that our implementation conforms to the HTML5 drag-and-drop processing model as defined in <http://dev.w3.org/html5/spec/Overview.html#drag-and-drop-processing-model>.

[Daniel Bates]

Created attachment 43269 [details]
Individual Layout test

For convenience, here is just the layout test. Modified to use WebKit.org absolute paths.

[Sebastian Markbåge]

(In reply to comment #3)
> Created an attachment (id=43269) [details]
> Individual Layout test
> 
> For convenience, here is just the layout test. Modified to use WebKit.org
> absolute paths.

I can indeed verify that this is has been resolved in the nightly r51280.

Note that dropEffect is undefined at the drop event as noted here: https://bugs.webkit.org/show_bug.cgi?id=24731#c52