moribvndvs / ng2-idle

Responding to idle users in Angular (not AngularJS) applications.
https://moribvndvs.github.io/ng2-idle
Apache License 2.0
315 stars 128 forks source link

Timeout is not occurring as per configuration - inconsistent behavior #62

Open devendrar opened 6 years ago

devendrar commented 6 years ago

I'm submitting a ... (check one with "x")

[ ] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/HackedByChinese/ng2-idle/blob/master/CONTRIBUTING.md#getting-help

Current behavior Whatever timeout is configured in settimeout the idle period and timeout did not end as per configuration. It has been observed that the last expiry value is not calculating it properly. Sometimes it did not fire timeout event after it occurs first time. This is mostly occuring when you set the large number in that timeout period.

Expected behavior

The timeout should happen whatever is configured in setTimeout.

Minimal reproduction of the problem with instructions Settimeout for 60 second interval and 60 seconds in setIdle. The timeout occurs at anytime or sometimes did not occur at all.

What is the motivation / use case for changing the behavior?

Please tell us about your environment: OS windows-10