Skip to content
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 guidance to the text input component to help users understand when to use input type="number" #1128

Closed
5 of 6 tasks
36degrees opened this issue Jan 15, 2020 · 2 comments · Fixed by #1144
Closed
5 of 6 tasks
Assignees

Comments

@36degrees
Copy link
Contributor

36degrees commented Jan 15, 2020

What

Add guidance to help users understand when it's appropriate to use input type="number"

Why

We have a lot of research that shows that input type="number" can be problematic and we believe that it should only be used in very specific contexts.

Done when…

  • We understand whether there are valid use cases for using input type="number" that outweigh the negatives (usability and accessibility issues)
  • We've drafted guidance to add to the Design System to help users understand when they should use it; when not; and what they should use instead
  • We've updated the html and nunjucks examples
  • Guidance 2i'd
  • Guidance published
  • Old url retired and redirected
@StephenGill
Copy link
Contributor

Suggested update to text-input guidance here: https://docs.google.com/document/d/1waXRg1DrwZgMVEQJkjLyNQ2bK5beatTcZPRxNekETtI/edit

Needs a review for accuracy from @hannalaakso

@hannalaakso
Copy link
Member

Thanks @StephenGill this is a great start! There's a lot to talk about when it comes to type="number" so maybe we should write the blog post first and then distil this content from there...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

Successfully merging a pull request may close this issue.

3 participants