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
Actually, nevermind -- this is an intended change with the fixes made to controlled usage of NumericInput in #4211. The new behavior is correct, but consumers may have been relying on buggy behavior of the component before that change. The recommendation is that controlled usage should always use the second parameter of onChange, taking the value as a string, rather than as a parsed number.
Environment
Code Sandbox
Link to a minimal repro (fork this code sandbox): https://codesandbox.io/s/nice-bartik-3ku3b?file=/src/App.js
Steps to reproduce
.
at the end of inputActual behavior
Nothing, keystroke is not registered
Expected behavior
Keystroke is registered and
0.
is shown in the inputPossible solution
This regression was caused by #4211, so we need to look there for solutions
The text was updated successfully, but these errors were encountered: