-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix for wrong mousemove event on Chrome browser #217
Conversation
This fix works well and resolved many issues... can you please merge this branch "asap" ?! |
Hello @HobieCat would you please sign our CLA so that I can merge your contribution. Sorry for the delay here, I was foolish and hoped Chrome would fix the bug they introduced, but I have now adopted the assumption that Chrome will not fix any of their browser bugs in a timely manner. I suppose once you have top browser share, you no longer have to care about little things like only generating a mouse move event if the mouse actually moved, rather than if some layer just disappeared that was under the mouse. Another fail on my part was messing up the repo watching after I changed it to an organisation. I am now notified correctly of all issues and PRs. |
Hi @thepag, I just signed your CLA. Nevermind about the delay. BTW, looks like the bug is still there in v39.0.2171.65... |
Cheers @HobieCat |
Going to merge this next. Think I'll change the check for undefined to better code:
Since anyone can do |
Ignore what I said about the destroy code... I'd thought that I've made some changes to the indentation so it matches the rest of my (OCD) indentation. I've changed some variable names, because they were verbose even by my standards 😄 I am using |
Yep, the |
I left the |
On Chrome 34.0.1847.132 browser running on Kubuntu 13.04, Windows Vista/7 and OSX in jPlayer fullscreen mode, the gui does the fadeIn/fadeOut a random number of times even when the mouse is not moving. Fixed by checking if the the mouse has been actually moved before doing the fadeIn/fadeOut.