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

Indicated dirty/validity state for unit-based inputs #42

Open
justin-hackin opened this issue May 15, 2021 · 0 comments
Open

Indicated dirty/validity state for unit-based inputs #42

justin-hackin opened this issue May 15, 2021 · 0 comments
Labels
~meal~ 3 story points user-facing Bugs or quirks that the user should be aware of

Comments

@justin-hackin
Copy link
Owner

justin-hackin commented May 15, 2021

Addresses:

  • No visual indication of invalid unit-based number input after enter-submission
  • Input does not re-insert unit on submission if erased (and the input label doesn't indicate unit)

The text input holds an intermediate value until the enter key is submitted. If the intermediate value matches the value in the property, it is valid. If the enter key was pressed but the input had invalid information, mark the field as errored. If the input text changes, mark as dirty.

State could be indicated with an icon inside input or with red/green background for field.

@justin-hackin justin-hackin added user-facing Bugs or quirks that the user should be aware of ~meal~ 3 story points labels May 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
~meal~ 3 story points user-facing Bugs or quirks that the user should be aware of
Projects
None yet
Development

No branches or pull requests

1 participant