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
Describe the bug
Eui field number gets stuck on natively invalid state when used as a controlled input and value is changed by any means other than interacting with the input itself.
Impact and severity
This bug makes the EuiFieldNumber input not useable as a controlled input that can be changed by means other than directly interacting with the input. This should be an easy fix.
You should see the warning icon on the right, indicating the input is natively invalid for exceeding its max value
Now click the button that says "set value to valid"
The value will change to a valid number, but the natively invalid warning icon will still be there. You have to focus and then blur the input to clear the invalid warning
Expected behavior
Ideally natively invalid state should be checked on any value change rather than just on blur or change via the input.
Minimum reproducible sandbox
See sandbox link in "To Reproduce" section
The text was updated successfully, but these errors were encountered:
Describe the bug
Eui field number gets stuck on natively invalid state when used as a controlled input and value is changed by any means other than interacting with the input itself.
Impact and severity
This bug makes the EuiFieldNumber input not useable as a controlled input that can be changed by means other than directly interacting with the input. This should be an easy fix.
Environment and versions
To Reproduce
9
Expected behavior
Ideally natively invalid state should be checked on any
value
change rather than just on blur or change via the input.Minimum reproducible sandbox
The text was updated successfully, but these errors were encountered: