607931 - "dropEffect" property of DataTransfer doesn't change when drag & drop link etc into other tabs or Window.

Status: RESOLVED DUPLICATE of bug 1777149

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

Description

[kamachi]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; ja; rv:1.9.2.12) Gecko/20101026 Firefox/3.6.12 ( .NET CLR 3.5.30729; .NET4.0E)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; ja; rv:1.9.2.12) Gecko/20101026 Firefox/3.6.12 ( .NET CLR 3.5.30729; .NET4.0E)

When drag & drop link etc into content area of other browser IE etc, "dropEffect" value change "copy" or "move".
But when drag & drop link etc into content area of other tabs or Window or other version Firefox`s window (not input area), "dropEffect" is still "none".

Reproducible: Always

Comment 1

[Nickolay_Ponomarev]

This report is not really clear. Please follow https://developer.mozilla.org/en/Bug_writing_guidelines when reporting bugs.

Comment 2

[kamachi]

To know the drop operation is not done (canceled or prohibited), I get the value of "event.dataTransfer.dropEffect" at dragend event in content area of window.

When the item may not be dropped, the possible "dropEffect" value is "none".
But even when drag a link(in content area) and successfully drop in to the content area of another tab or window (of firefox) and the link is opened, the value of "dropEffect" takes "none" .
So in above case, can`t determine what drop operation occurred from the value of "dropEffect".

Comment 3

[Nickolay_Ponomarev]

Thanks, but still if you provided a testcase and indicated what exactly one needs to do to reproduce the problem (and what the problem is), it would be much easier to move forward with the bug.

Comment 4

[Alex Reardon]

I can confirm this is still an issue. I'll try to give some more details.

Steps:

1. Create a draggable element
2. Drag the element from one browser tab to another (window A -> window B)
3. In the window B, successfully allow a drop operation on an element (call event.preventDefault() in dragenter and dragover on the drop target element)
4. In the dragenter and dragover events in window B, set the dropEffect (eg event.dataTransfer.dropEffect = 'move')
5. Drop the draggable element
6. A drop event fires in window B on the drop target with the correct dropEffect set ("move")
7. A dragend event fires in window A but the event.dataTransfer.dropEffect property is set to "none"

ꜛ Step 7. is the bug. Chrome v103 and Safari v15.5 both set event.dataTransfer.dropEffect to "move" in window A

Environment: MacOS 12.4

• Url to example: https://5ll6w4.csb.app/ (see the console)
• Url to codesandbox powering the example: https://codesandbox.io/s/dragging-between-windows-firefox-bug-5ll6w4?file=/src/index.ts

Comment 5

[Alex Reardon]

(In reply to Alex Reardon from comment #4)

I can confirm this is still an issue. I'll try to give some more details.

Steps:

1. Create a draggable element
2. Drag the element from one browser tab to another (window A -> window B)
3. In the window B, successfully allow a drop operation on an element (call event.preventDefault() in dragenter and dragover on the drop target element)
4. In the dragenter and dragover events in window B, set the dropEffect (eg event.dataTransfer.dropEffect = 'move')
5. Drop the draggable element
6. A drop event fires in window B on the drop target with the correct dropEffect set ("move")
7. A dragend event fires in window A but the event.dataTransfer.dropEffect property is set to "none"

ꜛ Step 7. is the bug. Chrome v103 and Safari v15.5 both set event.dataTransfer.dropEffect to "move" in window A

Environment: MacOS 12.4

• Url to example: https://5ll6w4.csb.app/ (see the console)
• Url to codesandbox powering the example: https://codesandbox.io/s/dragging-between-windows-firefox-bug-5ll6w4?file=/src/index.ts

Tested on firefox v101.0.1