-
Notifications
You must be signed in to change notification settings - Fork 29
🎨 [Frontend] UX Cookie Expiration Date #6066
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
🎨 [Frontend] UX Cookie Expiration Date #6066
Conversation
Q: Instead of asking the user to logout, why not to logout the user automatically and show the login page with "session expired. Please login again" as in other tools |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Comment above.
@pcrespov |
What do these changes do?
reported by @newton1985 .
When a computer goes into hibernation, the browser's setTimeout functions, along with other JavaScript timers, are paused. This is because the computer essentially saves the state of everything to disk and then powers off, halting all running processes including the browser.
In order to overcome the long setTimeout issue with hibernation (which was the case for the Cookie Expiration workflow), this PR changes the mechanism. We will now first set the expirationDate as a property and check every minute where we are with regards to the Expiration Date. If the user hibernates and comes back, this every minute check will kick again the continue with the workflow.
Animation with the cookie expiring in 15' and 1" check interval (after logging in, I Sleep the computer for a few seconds):

Related issue/s
How to test
Dev-ops checklist