Open TheSkylArk opened 7 years ago
The issue seems to be from the filter check for mousemove
if (event.type === 'mousemove'
&& ((event.originalEvent && event.originalEvent.movementX === 0 &&
event.originalEvent.movementY === 0)
|| (event.movementX !== void 0 && !event.movementX || !event.movementY))) {
return true;
}
in documentinterruptsource.ts
IE does not have the event.movementX
or event.movementY
property so I think this is causing the mousemove
event to always be filtered.
This is an issue for an app we're writing as well. For IE users on windows 8 or earlier, it causes issues (even with IE 11).
+1
mouse pointer spnning around on IE
while the pull Request isn't approved take a look into the chat in it where a kind of workaround is provided.
I'm submitting a ... (check one with "x")
Current behavior When using IE11 moving the mouse does not stop idle. (Using DEFAULT_INTERRUPTSOURCES)
Expected behavior On other browsers tested (Chrome, Firefox and Edge) moving the mouse stops idle timeout
Minimal reproduction of the problem with instructions Start up ng2-idle example https://hackedbychinese.github.io/ng2-idle in IE11. Wait for timeout countdown to start. Moving mouse does not stop countdown.
What is the motivation / use case for changing the behavior?
Please tell us about your environment:
@ng-idle version: 2.0.0-beta.4
Angular version: 2.2.1
Browser: IE 11
Language: [all | TypeScript 2.0.3 | ES6/7 | ES5]
Node:
node --version
= 6.9.1