-
Notifications
You must be signed in to change notification settings - Fork 27
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] Fix: Unique session id #6335
🐛 [Frontend] Fix: Unique session id #6335
Conversation
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.
great! thanks!
and this should survive to F5
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.
thx
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.
🙏 thanks a lot!
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.
👍🏼
Quality Gate passedIssues Measures |
What do these changes do?
Changes the logic to create/get the clientsessionid. When a tab gets duplicated, the
sessionStorage
andlocalStorage
get also copied. When this happens, two different tabs would end up using the same sessionId, bringing the user to buggy scenarios.This PR updates the getClientSessionId function, which now also relies on the
window.name
, which doesn't get copied when a tab is duplicated but it persists to window reloads.Related issue/s
closes #4363
How to test
Dev-ops checklist