Numeric inputs should only allow relevant characters to be input
Bug #534924 reported by
Jonathan Jacobs
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Methanal |
Invalid
|
Wishlist
|
Unassigned | ||
Bug Description
IntegerInput and DecimalInput will validate the input after losing focus but preventing irrelevant (non-digit, or periods in the case of DecimalInput) characters from being input in the first place is a better experience.
Perhaps building on FilteringTextInput would be the best approach.
| Changed in methanal: | |
| status: | New → Confirmed |
| importance: | Undecided → Wishlist |
| description: | updated |
| Changed in methanal: | |
| milestone: | none → 0.2.1 |
| Changed in methanal: | |
| status: | Confirmed → Invalid |
Revision history for this message
| Jonathan Jacobs (jjacobs) wrote | #1 |
To post a comment you must log in.
After chatting about this, I don't think trying to manipulate the user's input is something we want to do in general. I think having validators for DecimalInput and IntegerInput is a good approach will cause less confusion than attempting to filter the user's keystrokes in realtime.