Fix NumberInput seems buggy when used in a FilterForm #7830
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
NumberInput
The Filter Button/Form combo changes the filter value as the user types. But, as explained earlier in this page,
<NumberInput>
converts the input value to a number on blur.This means that using
<NumberInput>
in a filter form will not work as expected. The filter will only change when the user presses the Enter key, which differs from the other input types.In a filter form, you should use a
<TextInput type="number">
instead: