-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Fix #8404: V11 fixed the lack of an immediate value update #8405
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: v11
Are you sure you want to change the base?
Fix #8404: V11 fixed the lack of an immediate value update #8405
Conversation
|
Thanks a lot for your contribution! But, PR does not seem to be linked to any issues. Please manually link to an issue or mention it in the description using #<issue_id>. |
|
Hey @dmitrii-nikiforov, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Issue
InputOtp did not update the value immediately in onValueChange. Due to useState behavior, the callback received a stale value until the next render, causing incorrect OTP state handling.
Fix
The value update logic now ensures the latest tokens are used when triggering onValueChange, allowing the value to reflect immediately on input and paste events.
Impact
InputOtp now behaves as expected with instant value updates, improving correctness and developer experience in controlled usage.
|
Thanks a lot for your contribution! But, PR does not seem to be linked to any issues. Please manually link to an issue or mention it in the description using #<issue_id>. |
2 similar comments
|
Thanks a lot for your contribution! But, PR does not seem to be linked to any issues. Please manually link to an issue or mention it in the description using #<issue_id>. |
|
Thanks a lot for your contribution! But, PR does not seem to be linked to any issues. Please manually link to an issue or mention it in the description using #<issue_id>. |
|
Thanks a lot for your contribution! But, PR does not seem to be linked to any issues. Please manually link to an issue or mention it in the description using #<issue_id>. |
Fix #8404