The cursor doesn't update if a drop target changes the dropEffect or effectAllowed values

RESOLVED DUPLICATE of bug 1121946

Status

()

Core
Drag and Drop
RESOLVED DUPLICATE of bug 1121946
9 years ago
2 years ago

People

(Reporter: Sebastian Markbåge, Unassigned)

Tracking

unspecified
x86
Windows Vista
Points:
---
Bug Flags:
blocking1.9.2 -
wanted1.9.1 ?

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

9 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.0.7) Gecko/2009021910 Firefox/3.0.7 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1b3) Gecko/20090305 Firefox/3.1b3

When the user moves the cursor over a drop target that overrides the dropEffect or effectAllowed values during the dragenter or dragover events, the cursor isn't updated to the corresponding values.

Reproducible: Always

Steps to Reproduce:
Start a drag operation and during the dragstart event, set event.dataTransfer.effectAllowed = 'all';

During the dragenter and dragover events of a target element, set event.dataTransfer.dropEffect = 'copy';
or
event.dataTransfer.effectAllowed = 'copy';
Actual Results:  
The cursor now shows the "move"-cursor unless you use a modifier key.

Expected Results:  
The cursor should instead show the "copy" since the dropEffect or effectAllowed has been changed and the operation will be allowed to perform a drop.

Whether or not the user should be able to change the dropEffect using modifier keys after it has been explicitly overridden is not the point here. It's the fact that the cursor doesn't correspond to the current operation that will be performed.
(Reporter)

Updated

8 years ago
Flags: wanted1.9.1?
Flags: blocking1.9.2?
Flags: blocking1.9.2? → blocking1.9.2-

Comment 1

8 years ago
I have noticed the same problem on Firefox 3.5.5 on Mac OSX.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 1121946
You need to log in before you can comment on or make changes to this bug.