Nathan Carlson
Results
2
comments of
Nathan Carlson
> I suspect that it's because I forgot to wrap onChange in useCallback so "new" onChange handler causes this behavior. Please try that and let me know if it will...