-
Notifications
You must be signed in to change notification settings - Fork 4.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
Select does not display options initially when filterOption prop is specified #4504
Comments
I've also noticed this, as I used the workaround for limiting displayed options in large sets, which no longer works. |
Interesting side note; |
After some debugging, I've found that it's this change that broke it. #3990 |
Greetings, Thanks for the find @h3rmanj ! Some next steps I think to put around this:
Thoughts? |
I agree with 1, and have made a PR in #4514. I did them in seperate PRs so they could be addressed individually. Either would solve this issue, but both would be nice to have. Edit: Opened a feature request as well in #4516 |
Version
3.2.0
seemed to introduce an issue where options are not displayed when there is not input value and thefilterOption
prop is present. This worked fine in version3.1.1
Working example
https://codesandbox.io/s/311-working-301yt
Nonworking example
https://codesandbox.io/s/320-not-working-ibgc7?file=/example.js:389-445
To reproduce, click the select in both examples and notice that options are only displayed in the
3.1.1
example. Options are however rendered when there is an input present in the3.2.0
example.Thanks!
The text was updated successfully, but these errors were encountered: