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
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.
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...
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