What is being proposed?
As picked up by Atlas #143, the NumberInput currently shows user-entered invalid values, but does not commit them. As such, any form populated and used for further action may use outdated values.
Why is this needed?
Current behaviour of components which act on inputs from NumberInput is unpredictable for the user, as invalid values are shown as true to a user, but not committed. This could be tracked by an accessible error state which other components can use to disable on an invalid entry.
What will change?
Depending on implementation methods, this may change component interface, behaviour of committing an invalid value, etc.
Interface changes (if any)
Potentially, but undetermined.
Breaking change?
Next steps
A maintainer will review this issue.
If accepted, it will be marked as accepted and a PR may then be opened.
What is being proposed?
As picked up by Atlas #143, the
NumberInputcurrently shows user-entered invalid values, but does not commit them. As such, any form populated and used for further action may use outdated values.Why is this needed?
Current behaviour of components which act on inputs from
NumberInputis unpredictable for the user, as invalid values are shown as true to a user, but not committed. This could be tracked by an accessible error state which other components can use to disable on an invalid entry.What will change?
Depending on implementation methods, this may change component interface, behaviour of committing an invalid value, etc.
Interface changes (if any)
Potentially, but undetermined.
Breaking change?
Next steps
A maintainer will review this issue.
If accepted, it will be marked as
acceptedand a PR may then be opened.