-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Nag UI when some of your own devices are not verified by you #11220
Comments
The current thinking now is that this will be the same "new sign-in" toast as #11218, but potentially saying "unverified" instead of "new" for devices aren't actually new. |
Is a toast right to represent this? It's not a real-time event, and you device will still be unverified if you dismiss the toast. If we do want a toast:
|
Let's ping @nadonomy for thoughts here. At the moment, the current implementation shows "new session" toats for both real time new sessions as well as all pre-existing unverified sessions, so existing users can be slapped by a large stack of toasts to work through. |
Implement the three differenty cases for this session, and also fix ones for other sessions which had the wrong copy. Fixes element-hq/element-web#11220
nag barnew sign in toast.Q: Does this also apply if the device itself is not verified? Or should that be a different thing?
A: This is the 'Skipped Verify' toast: https://www.figma.com/file/wwqBo5oAFfk8XKmtd2YaIs/Cross-signing?node-id=38%3A16
The text was updated successfully, but these errors were encountered: