-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
If you miss the "unverified session" toast, it's very unclear how to verify the new session. #12857
Comments
cc @nadonomy |
This is a casualty of us descoping Settings from the phases to date. Should we re-assign this to the same phase Settings is in, or close it given the work is already captured? |
I'll mark this as after release for now. (Ah, it already is tracked as phase 4 / after release.) |
Moved to the separate story about device mgmt. |
D'oh, I didn't realise phase:4 was post release. We can talk more on Matrix, but I wonder if we should find a way to label so we don't need to remember arbitrary numbers. |
for now can “later“ show you a popup telling you to check your memberinfo to resume? |
It could, or maybe the toast itself could state something about this...? Over to @nadonomy for design thoughts. |
Yes, the number labels are too mysterious, I think most people agree. Filed element-hq/feature-dashboard#72 to find a better way. |
The list of sessions (in the "Security & Privacy" setting section) contains information like ID, name and last seen, but no button to perform the trusting procedure or a display of the trust state. There should be both for each device. |
…ary_move Move General user settings styles to more specific places
If I hit 'Later' on the unverified session toast (or if i have to cancel the verification for some reason), how do I resume?
I assume I need to reopen my memberinfo in an e2e room and then find the new login and verify it? This is a very unintuitive thing to do - I'd ideally expect to find it in Settings: Security rather than thinking to look in my own MemberInfo? Or at least some copy or a link from there to take you to the right place?
The text was updated successfully, but these errors were encountered: