You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am reporting this as a bug because this is behavior we did not see in the older (non-hook) version of the library. If the computer is sleeping when the promptBeforeIdle time would have triggered onPrompt, when the computer wakes up, it does not display the prompt. Also, once the timeout time elapses after sleep, onIdle is only fired once some action is taken in the browser window. This is also something we didn't see in the older version of the library.
Reproduction Steps
https://stackblitz.com/edit/stackblitz-starters-kyfpdb?file=src%2FApp.tsx
Assumptions:
timeout: 120 seconds
promptBeforeIdle: 15 seconds
1. Start the timer
2. Keep track of the time outside of the computer and put the computer to sleep
3. Wake the computer up after 1 minute 45 seconds
4. `onPrompt` will not fire
5. After the `timeout` elapses, nothing happens until the user clicks in the window.
Relevant log output
No response
Screenshots or Additional Context
No response
Module Version
5.7.2
What browsers are you seeing the problem on? Select all that apply.
Chrome
What devices are you seeing the problem on?
Desktop
Verification
I have checked for existing closed issues and discussions.
The text was updated successfully, but these errors were encountered:
@SupremeTechnopriest : Is there any estimate on resolving this sleep idle timer issue ? I am also using this library in my application, and auto logout is not happening properly , when the system goes to sleep mode .
What happened?
I am reporting this as a bug because this is behavior we did not see in the older (non-hook) version of the library. If the computer is sleeping when the
promptBeforeIdle
time would have triggeredonPrompt
, when the computer wakes up, it does not display the prompt. Also, once thetimeout
time elapses after sleep,onIdle
is only fired once some action is taken in the browser window. This is also something we didn't see in the older version of the library.Reproduction Steps
Relevant log output
No response
Screenshots or Additional Context
No response
Module Version
5.7.2
What browsers are you seeing the problem on? Select all that apply.
Chrome
What devices are you seeing the problem on?
Desktop
Verification
The text was updated successfully, but these errors were encountered: