-
Notifications
You must be signed in to change notification settings - Fork 372
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
Incorrect behaviour when entering <html> (instead of leaving) #38
Comments
agreed. same behavior on Firefox 29.0.1, Windows 7 x64 |
Thanks @s16h, we can look into Have you have a chance to run the script with /cc: @bergerjac |
I haven't tried yet. I'm going to fork and try to fix this later today (or possibly over the weekend). |
👍 |
According to MDN example, which illustrates the difference between
using only
var test = document.getElementById("discussion_bucket");
test.addEventListener("mouseout", function( event ) {
event.target.style.color = "red";
setTimeout(function() { event.target.style.color = ""; }, 2000);
}, false); |
This is great @bergerjac! Here's another way to test: Mouseout $('body').on('mouseout', function(e) {console.log('out')}); Mouseleave $('body').on('mouseleave', function(e) {console.log('leave')}); Want to submit a PR? |
…ates to contributing; - Issue carlsednaoui#38 carlsednaoui#38 explains why the change from mouseout to mouseleave
…ates to contributing; - Issue carlsednaoui#38 carlsednaoui#38 explains the change from mouseout to mouseleave
Closed with #45 |
If you load the page when the mouse pointer is still in the bar of the browser (say, on the address field) and after the page is loaded you moved the mouse onto the page to start looking at the website (as you do), the modal will get activated (at least that's the behavior in Chrome Version 34.0.1847.116 m on Windows 7).
I think instead of
mouseout
,mouseleave
should be used.The text was updated successfully, but these errors were encountered: