-
Notifications
You must be signed in to change notification settings - Fork 31
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
Click does not set input value #25
Comments
Is this feature still desired? |
Yeah, it's still desired. I've had a PR open for it for the last two years :) |
Sorry I didn't address this earlier. I think that in theory this component should always be controlled. Why ?
Having said that, I think we should fix #27 so that it always behaves a sa controlled component. What does everyone think ? Again I am sorry for jumping in late on this one. |
We do not currently allow the input value to be set by the user, do we? |
You are right. We don't do that. So we should add a prop that can directly take the value that needs to be shown from the user instead of handling it ourselves. |
If an option gets clicked,
input.value
does not get set as one would expect.The text was updated successfully, but these errors were encountered: