-
Notifications
You must be signed in to change notification settings - Fork 987
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
Always show the "I understand my password can't be recovered" disclaimer on password creation screen #15518
Labels
Comments
if this issue issue is still open, I would like to work on this issue |
@cammellos pinging you to confirm the assignment |
Sure, I'll assign it to you @SilentCruzer ! |
SilentCruzer
added a commit
to SilentCruzer/status-mobile
that referenced
this issue
Apr 14, 2023
SilentCruzer
added a commit
to SilentCruzer/status-mobile
that referenced
this issue
Apr 14, 2023
SilentCruzer
added a commit
to SilentCruzer/status-mobile
that referenced
this issue
Apr 14, 2023
SilentCruzer
added a commit
to SilentCruzer/status-mobile
that referenced
this issue
Apr 15, 2023
flexsurfer
pushed a commit
that referenced
this issue
Apr 17, 2023
alwx
pushed a commit
that referenced
this issue
Apr 28, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Report
Followup of #15405
Problem
Currently, according to design, we only show the disclaimer
I understand my password can't be recovered
when the user sets the cursor to the second input field (Repeat password
) .But if the user after that presses on the first input field (
Type password
) again for some reason, for example, if they add more characters to the password in the second field first and then back to the first and close the keyboard, then the disclaimer, that is needed to complete this step, won't be shown on the screen, which may be a bit confusing.video_2023-03-28_14-39-32.mp4
Expected behavior
We should consider the option to show the disclaimer on the screen always from the beginning / always when both password fields are filled
Actual behavior
The disclaimer is only shown after focusing on the second field
Reproduction
Type password
field and try to complete the password creation flowAdditional Information
The text was updated successfully, but these errors were encountered: