Open
Bug 905056
Opened 11 years ago
Updated 2 years ago
dropEffect is always NONE for cross-app drag
Categories
(Core :: DOM: Copy & Paste and Drag & Drop, defect)
Tracking
()
UNCONFIRMED
People
(Reporter: fb+mozdev, Unassigned)
References
()
Details
(Keywords: parity-chrome)
As observed by Ian Hickson (http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2013-August/040484.html):
> I've updated the spec. The trick is to check event.dataTransfer.dropEffect
> in the dragend event; if it's "none" then the drag was canceled.
>
> This works already in Chrome and Firefox for same-page drags; it also
> works in Chrome for cross-app drags, but in Firefox for some reason you
> always get "none" for cross-app drags currently. It does work for
> cross-page (all within Firefox) drags in Firefox. (Tested on Mac.)
|
Reporter | |
Updated•11 years ago
|
Component: General → Drag and Drop
Whiteboard: [parity-chrome]
|
||
Comment 1•7 years ago
|
||
Mass bug change to replace various 'parity' whiteboard flags with the new canonical keywords. (See bug 1443764 comment 13.)
Keywords: parity-chrome
Whiteboard: [parity-chrome]
|
||
Comment 2•2 years ago
|
||
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•