I have tested this on Windows under the current release of Chrome (18.0.1025.162 m) and Safari 5.1.5 (7534.55.3). How to reproduce: 1) Create a non-empty web page (just enought content to make it scrollable) 2) attach a handler to window.onmousemove and have it output clientX/clientY to the console. 3) Load the page into the browser, reduce the window size so that the page can be scrolled, and bring up the console window 4) Scroll the page down some 100 pixels or so. 5) Slowly move the mouse from the top of the client window downward. Notice how events stop firing when reaching a vertical position that is equal to the height of the client window minus the scrolled amount (e.g. if the window is 400px high and you scrolled down 100px, events will stop firing at clientY=500)
Could you please attach your example to the bug?
I'm sorry. I thought reproducing this bug was trivial, but as I tried to do so just now, I found this not to be the case at all. Unfortunately, the site on which the bug does appear is not online yet. I'm going to check tomorrow whether it's possible to give you public access. Let me say again I'm sorry. I thought it better to report the bug right away, I should have guessed it wouldn't be so easy to reproduce, otherwise everyone would know about it... -- Jean-Pierre
Here's a jsfiddle demonstrating this issue: http://jsfiddle.net/khqZk/3/ Basically the mousemove fires normally when the page isn't scrolled but once you scroll far enough the mousemove event stops firing. Another thing is that if you keep your left mouse button down while in this "mousemove dead area", the mousemove events start firing again.
(In reply to comment #3) Thank you Petka. I was unable to do more work on this issue.