> Did you try to use the native JavaScript implementation to observe the
> event? If not, please try it and post the results here; Maybe the
> doubled event firing is a browser bug.
Using the code:
var doc = document.documentElement;
doc.onmousemove = function(e){ console.log(e.pageX+', '+e.pageY); }
Safari 4 still appears to double fire on each mousemove.
I think this is a browser bug! It's the sort of browser bug that
jQuery specialises in fixing.
The fix I've got so far involves comparing [e.pageX, e.pageY] against
a stored [e.pageX, e.pageY] from the last mousemove before deciding to
do something. Creates a bit of an annoying overhead on mousemove,
though, particularily annoying for browsers that don't have the bug.
Anyone any ideas about how to feature detect it?
Stephen.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"jQuery Development" group.
To post to this group, send email to jquery-dev@googlegroups.com
To unsubscribe from this group, send email to
jquery-dev+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/jquery-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
