-
-
Notifications
You must be signed in to change notification settings - Fork 32.3k
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] Native built-in search in select boxes #10972
Comments
If by search you mean the way the native element supports it - focussing the first entry whose beginning that the entered characters match, then that seems like a sensible feature to support. I don't believe it has been intentionally omitted. @oliviertassinari any objections, or otherwise, any thoughts on implementation approach? |
It's a duplicate of #8191 |
There's a misunderstanding here. I was not talking about simply entering letters and the search component automatically highlights a value, but instead that you can FILTER the list of the select For example: Take this screenshot of an opened select box. You have a text field as "first entry" and if you enter something along the lines @oliviertassinari or @mbrookes Would it be possible to reopen this? |
@tzfrs Thanks for the clarification. It's something you should be able to build with any of the 3 different autocomplete libraries. |
I saw them, but they are doing it a bit different from the result I would expect. Anyway, I'm going to try it out if I can somehow get the result I want. I'll report back! |
Context
Hi, for a feature we're developing right now we want to use select boxes that are searchable. I found this demo section: https://material-ui.com/demos/autocomplete/ where
react-select
KINDA does what we want, however the result design is different from what we want. We want the same style as the selectboxes from this repo AND we want to search in the opened select box, NOT where the label/selected value is.Now I have two questions:
I ask because I forked this project, read the
CONTRIBUTING.md
and the first sentence was to check with the maintainers first, if a PR would be okay for a specific feature.The text was updated successfully, but these errors were encountered: