-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
AutoComplete: ForceSelection reseting value on blur events even if no changes is made. #2176
Comments
Problem still occurs in version 7.2.1. Can you guys solve it in 8.0.0 version? |
PR submitted. Will hopefully be merged for 8.0.0-rc2 |
@melloware, this is still happening in the latest version. Could you please check this again? With the |
@sandrocsimas i think that is intentional when forceSelection? Is your reproducer the same as the original in this ticket? |
@melloware I created that example from scratch in Codesanbox. I don't think that is the intentional behavior of |
This issue has been automatically marked as stale. If this issue is still affecting you with the latest version, please leave any comment, and we will keep it open. We are sorry that we have not been able to prioritize it yet. If you have any new additional information, please include it with your comment! |
Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please create a new issue with up-to-date information. Thank you for your understanding! |
I'm submitting a ... (check one with "x")
Codesandbox Case (Bug Reports)
https://codesandbox.io/s/damp-frog-znwfk
Current behavior
The Autocomplete componente reset value of field ( Calling onChange ) event if no change is made and value is setted.
Expected behavior
Force selection should reset value only if no valid value is setted
PrimeReact Version: The last one
The text was updated successfully, but these errors were encountered: