If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

JS Drag & Drop completly broken this time

RESOLVED INVALID

Status

()

Core
Event Handling
RESOLVED INVALID
16 years ago
15 years ago

People

(Reporter: Marc Boullet, Assigned: joki (gone))

Tracking

Trunk
x86
Windows NT
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

16 years ago
I just updated from 20010202 to 2002020512. NT4 SP6 300MHz

JS drag and drop, that was somehow buggy (see bug #114852), is
now not working at all, i.e. what was happening some times
in 114852 (and never at the first drag) is now always happening.

to see the problem
      http://bugzilla.mozilla.org/showattachment.cgi?attach_id=61431

or
      http://bugzilla.mozilla.org/showattachment.cgi?attach_id=61738
(Reporter)

Comment 1

16 years ago
It seems that once the original onmousedown has been
triggered, the mouse is not allowed to go outside of
the target of the OMD event. When it gets out, the
"ΓΈ" is displayed and it seems that all mouse events
(onmousemove and onmouseup) go, under this condition,
to the garbage can.

However, once the mouse button hes been depressed,
onmousemove works normally (as far as an event listener
for it is active).

Before, it was an annoying bug for those using D&D, now
it makes unusable pages that use D&D.

Comment 2

16 years ago
Created attachment 68155 [details]
working version

By adding return false; to the grabElm() function you prevent the browser from
'picking up' the image, and it keeps it's focus on the element.  The problem
you're seeing is the browser thinks you're trying to drag the image from the
document... Click and drag any image and you get the (\) while your on the
page...
(Reporter)

Comment 3

16 years ago
Ok, your're right.
"return=false" is the old way (pre DOM 2) to tell that the default action
for the event should not be triggered.

For DOM events (test case 2), if I add the statement e.preventDefault()
everything is all right.

Resolving as INVALID
Status: UNCONFIRMED → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → INVALID

Updated

16 years ago
QA Contact: madhur → rakeshmishra

Updated

15 years ago
QA Contact: rakeshmishra → trix
You need to log in before you can comment on or make changes to this bug.