1323170 - Drag operation gets aborted when dragover target is replaced

Status: NEW

(Core :: DOM: Copy & Paste and Drag & Drop, defect)

Description

[Marijn Haverbeke]

Attachment: test.html

When a dragover handler replaced the event's target with another node, no more events are fired for the drag operation (not even on completely separate nodes), and when a drop happens, its `clientX`, and `clientY` are still pointing at the place where the drag stopped working, not the actual drop position.

dragenter seems to have a similar problem.

In the attached file, drag something over the box, and notice that the events stop being logged as soon as you hit the second paragraph (which is replaced when dragged over).

Comment 1

[:Gijs (he/him)]

Flipping a coin between DOM: Events and Drag and Drop, this is where I ended up going, but maybe my coin was loaded? Olli or Neil, do you know what's going on here?

Comment 2

[Neil Deakin]

I see this issue in a release build, but not in my local build.

Comment 3

[Neil Deakin]

Actually, after more testing, I only see this issue on Linux.