Reply to thread

Message: [QUOTE="Thomas 'PointedEars' Lahn, post: 4982772"] Probably because you are changing the `src' property of the object being clicked on mousedown and onmouseup. That causes a change of cursor shape here[1] (because the image is loading), and the trigger coordinates of the background hourglass cursor (`progress') might be slightly different than those of the default cursor (`pointer'). That appears to be a known peculiarity of the MSHTML DOM (it was pointed out to me with regard to hoverMe). Check the window.event.fromEvent and window.event.toEvent properties to find out. If your code is starting to think, you better call Stockholm ;-) See above. Yes, that's the Gecko DOM. I think you need to prevent the default action of the corresponding event. If you use Firebug's Log Events feature on the `img' element and its parent, you will see that (at least) the following events occur when dragging the image: mouseover, mousemove (in that order); draggesture, dragenter, dragover, dragexit; mouseover, mousemove, mouseout (in that order). Good luck! PointedEars [1] "Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1)" from IEs4Linux 2.99.0.1 beta on wine-1.0.1-174-gc4039bd on Debian GNU/Linux stable/lenny/unstable on Linux 2.6.27.8-20081225.024056+0100 PREEMPT i686 [/QUOTE]