-
-
Notifications
You must be signed in to change notification settings - Fork 32.4k
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] Port component #4783
Comments
I have been playing around with react-autosuggest today of @moroshko. I have found this library pretty great. I think that we can provide an integration example or a small wrapper around it should be enough to close this issue and the other 55 issues. It's accessible, well tested, lightweigh, well documented and allow enough customization power for us. |
* #4783 - As discussed on #4393 and #4783 I have provided a fix for popover position issue on autocomplete. * Update Popover.js * -Commented PR changes are applied -Prop name is changed to a more meaningful name * Update Popover.js * Prop order is changed as alphabetical order * redundant space removed * redundant space is removed
* #4783 - As discussed on mui/material-ui#4393 and mui/material-ui#4783 I have provided a fix for popover position issue on autocomplete. * Update Popover.js * -Commented PR changes are applied -Prop name is changed to a more meaningful name * Update Popover.js * Prop order is changed as alphabetical order * redundant space removed * redundant space is removed
Is there any other solution than this wrapper? Seems like we are forced to use a wrapper even if the field is not MUI Autocomplete . Any findings for Mui Input or TextField? @oliviertassinari |
Please rethink, redesign, rewrite.
The text was updated successfully, but these errors were encountered: