-
Notifications
You must be signed in to change notification settings - Fork 2
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
fix(fe:FSADT1-1006): Display numeric keyboard without classifying the field as a telephone #843
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
|
fterra-encora
force-pushed
the
feat/FSADT1-1006-number-input
branch
from
March 11, 2024 14:42
98fc055
to
7d48771
Compare
|
Frontend component Test CoverageCoverage after merging feat/FSADT1-1006-number-input into main will be
Coverage Report
|
Frontend e2e Test CoverageCoverage after merging feat/FSADT1-1006-number-input into main will be
Coverage Report
|
paulushcgcj
approved these changes
Mar 11, 2024
19 tasks
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Uses inputmode="numeric" instead of type="tel", unless the field indeed refers to a telephone value.
This prevents screen readers from announcing the field as a telephone when it's not.
Fixes FSADT1-1006
Type of change
How Has This Been Tested?
Checklist
Further comments
Thanks for the PR!
Any successful deployments (not always required) will be available here
Once merged, code will be promoted and handed off to following workflow run.
Main Merge Workflow
Thanks for the PR!
Any successful deployments (not always required) will be available here
Once merged, code will be promoted and handed off to following workflow run.
Main Merge Workflow