Inconsistent between two different computers about ng-idle

[nhirakawa]

I've seen this behavior as well. It seems to be a bug in Chrome (https://code.google.com/p/chromium/issues/detail?id=170631), but I've also seen the behavior in IE.

I modified my local copy to only reset the timer on mousemove if the mouse has moved more than 5 pixels. This helped a lot, but I'm still seeing inconsistencies across computers, even with the same OS and browser.

[moribvndvs]

I have heard of mousemove bugs now and again, but I've never actually seen them myself (I figured there were mitigating circumstance, input device drivers or something like that). I've been working on Chrome under OSX and Windows and have not seen it (on a MacBook and also a Dell), so it'll be hard for me to fix it without reproducing it. Assuming it is the continuous mousemove feedback, of course.

@nh0815, if you're willing to share your changes, I'd like to take a look at how you solved it. It seems reasonable to follow your line of thought and just record the last coords if the interrupting event is mousemove and compare to current, throwing the event out if they are the same.

[sdawson26]

Now that I think of it, computer 2 uses a special crazy gaming mouse (its very sensitive). That could be the root of the problem. I'm going to ask my colleague to switch to a basic mouse and see if that does anything.

EDIT: Nevermind! The mouse had nothing to do with it

[moribvndvs]

Drivers still, maybe? I also wonder if there is some software running that tries to keep the computer from going idle and showing the screen saver by artificially reporting mouse input. Or something like that.

Well, anyways, we would still need to solve the issue. @nh0815's suggestion sounds lightweight and unobtrusive enough, I just wish I could see it fixed rather than just assume it's fixed when the change is made.