-
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
Me: Use FormTelInput instead of FormTextInput #1399
Conversation
There's not a lot to say about this until the mobile work is done. If this is a visual regression for mobile I'm not sure we should merge it before fixing up the layout. I wish there was a way to feature-flag an already-launched feature or something. |
88f0ab4
to
8324348
Compare
looks good to me |
context: '7 digit two factor code placeholder.', | ||
textOnly: true | ||
} ), | ||
eightDigitBackupCodePlaceholder: i18n.translate( 'e.g. 123456', { |
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.
Shouldn't the example be 12345678 ?
8324348
to
dd6b9ec
Compare
I just tested the app and it works really well. Great work Eric! |
Me: Use FormTelInput instead of FormTextInput
Fixes #28
This PR replaces the
FormTextInput
components that were being used throughout 2fa withFormTelInput
which should show a number keyboard on mobile devices.While working on that fix, I also updated placeholders to be consistent with #1386
cc @rickybanister for design review and @johnHackworth for code review.
After screenshots (Note: mobile layout will be worked on in other PRs):
To test:
fix/me-2fa-number-input
branch/me/security/two-step
and enable/disable 2fa for a test account.Note: In the below screenshots the label and button in the application passwords section header seems off. I'm not sure what to do there, but it is unrelated to this PR.
After screenshots: