Webkit and Safari Fire mousemove, even if the mouse does not move

Question

I read about the problems when the mousemove event is mousemove twice in Safari / Webkit, but the problem I am facing is that mousemove fires even if the mouse is not moved, That is: it fires already when the mouse cursor is over the context to which the event is attached when the page is loaded / updated. And since I am attaching it to document (full browser viewing screen), it starts right away in Safari. I tried attaching it to the html element, to body and to the wrapper of the div . Without changes.

 $(document).bind('mousemove', function() { alert('Mouse moved!'); $(document).unbind('mousemove'); }); 

Is works fine in other browsers. Does anyone see what I'm doing wrong? Thanks.

Answer 1

I know its a dirty hack, but at least it's something: just execute the callback function a second time to mousemove .

 var $document = $(document), i = 0; $document.bind('mousemove', function() { if (++i > 1) { alert('Mouse moved!'); $document.unbind('mousemove'); }; }); 

Demo: http://fiddle.jshell.net/Yz5Bd/show/light/

For what it's worth, Safari is not the only browser launching mousemove when the page loads - IE does this too. In any case, people using other browsers do not notice the “delay”, since it is almost impossible to move the mouse only one pixel.