UNCONFIRMED 101853
wrong dropEffect ("copy") on dragend when current operation is "move" 
https://bugs.webkit.org/show_bug.cgi?id=101853
Summary wrong dropEffect ("copy") on dragend when current operation is "move"
danya.postfactum
Reported 2012-11-10 20:46:33 PST
Created attachment 173483 [details] This demonstrates wrong dropEffect on dragend when current operation is "move" Open the attachment in Chrome on Windows 7. Open Console. Check "move" dropEffect (current operation) radiobutton. Grab the link and drop it on document somewhere. You get: event: dragend dropEffect: copy instead of: event: dragend dropEffect: move Play with another dropEffect's. "copy", "link", "none" are passed to dragend event correctly. This bug presents on Windows only. Tested in Chrome 22.
Attachments
This demonstrates wrong dropEffect on dragend when current operation is "move" (1.80 KB, text/html)
2012-11-10 20:46 PST, danya.postfactum 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
danya.postfactum
Comment 1 2013-01-24 07:39:45 PST
I think it is serious bug, which brokes d'n'd reqular handling. Why is it still UNCONFIRMED ?
Lucas Forschler
Comment 2 2019-02-06 09:18:33 PST
Mass move bugs into the DOM component.
Jay C
Comment 3 2019-10-01 12:42:30 PDT
I am running into this as well macOS 10.14.6 (18G95) Safari 13.0.1 When dropping an element that has effectAllowed: copyMove, I am receiving dropEffect: none, and my effectAllowed is changing to "copy" if I have the altKey pressed. Firefox has the correct behavior of dropEffect changing to copy or move depending if the altKey is pressed. -- Another bug that comes along with this is altKey isn't changing to true/false as I drag and press/release the key. I have to start the drag with the altKey pressed, or not pressed. Firefox behaves correctly when pressing/releasing the altKey while in a drag.
Note You need to log in before you can comment on or make changes to this bug.