You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I believe this is due to how the react-aria number input works. It takes the value in the input and applies it on blur. Though maybe if the submit button is enabled when the input is touched it would still submit (and update the number value)?
The onChange event is triggered whenever the number value updates. This happens when the user types a value and blurs the input, or when incrementing or decrementing the value. It does not happen as the user types because partial input may not be parseable to a valid number.
If it's hard to fix on the input side, I lean toward leaving the button enabled and having it refuse to submit if the values haven't changed. Might as well enable it to begin with if it's going to be enabled on touch. We could also hack something into the field's onChange to enable the button.
2025-01-09-resize-input-blur.mp4
The text was updated successfully, but these errors were encountered: