-
Notifications
You must be signed in to change notification settings - Fork 338
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
Add extra tracking modifier for inputs #1222
Conversation
We could raise this on the backlog as a suggestion, since this could be quick for service teams to implement and try out? |
Thanks for picking this up, I’d be really happy to see it go into the Design System. Couple of thoughts: Naming thingsWould SpacesSomething that came up discussing this with @tombye Should there be/is there some associated guidance about being forgiving about spaces being typed in these kinds of field? There’s some discussion on the phone numbers issue in the backlog already, but it feels like a wider thing than that. People often use spaces to ‘chunk’ long numbers (phone numbers, credit card numbers, licence numbers) to make them easier to transcribe. Services should be forgiving of this and not respond with validation errors. |
9272deb
to
048d555
Compare
Closing this for now as it's been deprioritised. |
@36degrees @timpaul any chance of resurrecting this? I think it could be useful for a number of patterns asking for numerical codes, including security (2FA) codes. |
This adds a
--extra-tracking
modifier for inputs which increases the tracking, and turns on tabular numbers.The idea is that this modifier would be used for inputs asking for e.g. reference or phone numbers, where the user would be checking back one character at a time.
This was inspired by alphagov/notifications-admin#1545
Without modifier
With modifier
Questions…
--extra-tracking
?1ex
has a different width?