forked from nzakas/yui-misc
-
Notifications
You must be signed in to change notification settings - Fork 144
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
On startup mousemove is ignored #23
Comments
Issue number 1 from my summary is fixed with the following
Although it was just me not thinking, may want to add that to the demo. I don't know? |
I've achieved the expected behavior for issue number 2 from my summary with the following changes
Please consider these changes for the main branch. |
These fixes and more are in my fork https://github.com/thorst/jquery-idletimer/blob/master/src/idle-timer.js |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm still experiencing the issue I described in #16 (comment). However now I have had time to investigate what I was experiencing.
Tested on 2/27/2014 with Chrome Version 33.0.1750.117 m && Firefox 27.0.1.
Im testing https://raw.github.com/mikesherov/jquery-idletimer/master/dist/idle-timer.js
Here's how reproduce it.
Details
The mouse move event is triggered (line 97). obj.idle (line 106) is false, so it never triggers the toggle until the timeout expires once.
I havent tracked it down, but it seems like the textareas timer is triggering for the document timer, and thats why #status shows as idle (step number 2 above)
Issue
This isn't an issue when the timeout is 5 seconds, because it will go in and out of idle state frequently.
But my timeout is high (13 minutes) so for it to perform this cycle, its too late and my server side's session has expired.
Side Note
I thought just setting idle to true or startImmediately to false (or both) would be enough. But the result is the same, after the timeout the banner shows idle even though I'm moving my mouse.
Looking at #1 I believe a fix for that would solve my issue. However, i still need to support ie8, so the proposed fix (pagevisibility) wouldn't work.
Summary
I beleive there are 2 issues:
The text was updated successfully, but these errors were encountered: