Skip to content
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

"New login. Was this you?" popover is persistent and can't be dismissed #18603

Closed
kittykat opened this issue Aug 17, 2021 · 6 comments
Closed
Labels
A-E2EE-Cross-Signing A-Toast O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect X-Cannot-Reproduce X-Needs-Info This issue is blocked awaiting information from the reporter

Comments

@kittykat
Copy link
Contributor

Steps to reproduce

  1. Log into Element from another platform

What happened?

This popover is persistent:
Screenshot from 2021-08-17 20-47-19

The "Check your devices" button opens the "Where you’re logged in" settings window.
The "Later" button doesn't do anything.

What did you expect?

Being able to dismiss the dialog in some way

Operating system

Arch Linux

Browser information

Chromium Version 92.0.4515.131 (Official Build)

URL for webapp

develop.element.io

@SimonBrandner
Copy link
Contributor

Does this freeze the whole app? It might be a duplicate of #17667

@SimonBrandner SimonBrandner added A-E2EE-Cross-Signing A-Toast O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Major Severely degrades major functionality or product features, with no satisfactory workaround X-Needs-Info This issue is blocked awaiting information from the reporter labels Aug 18, 2021
@dbkr
Copy link
Member

dbkr commented Aug 18, 2021

I still can't repro it though

@kittykat
Copy link
Contributor Author

Does this freeze the whole app? It might be a duplicate of #17667

No, the rest of the app worked fine and I can't reproduce it now either. Will /rageshake and reopen if it comes up again.

@kittykat
Copy link
Contributor Author

kittykat commented Sep 3, 2021

Rageshake submitted. I'm using same browser, normal and private sessions, for both element sessions. The toast pops us first, then gets the authentication toasts stacked in front of it and when those are dismissed/actioned/go away, the new login one is persistent.

@dbkr
Copy link
Member

dbkr commented Sep 8, 2021

As per above PR, there's now some logging on develop to debug this: if anyone sees this again, please submit debug logs & mention this issue.

@robintown
Copy link
Member

This is in fact a duplicate of #17667. Confusingly, the title of that issue is not referring to the entire UI being frozen, just the toast.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-E2EE-Cross-Signing A-Toast O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect X-Cannot-Reproduce X-Needs-Info This issue is blocked awaiting information from the reporter
Projects
None yet
Development

No branches or pull requests

4 participants