You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using AutoComplete with filtering for selecting options from hundreds of items. But when we specify filter and only one option is visible in suggestions, pressing enter should allow to select it (trigger onNewRequest with this item). Now user have to use keydown to select option and then press enter to select the option. It is a little annoying, especially that using keydown with AutoComplete and openOnFocus is problematic as described in #4922
I know that it can break some functionality with selecting values not listed. But connecting this feature with #5494 can give a great user experience.
Link to minimal working code that reproduces the issue
For people that come across this issue. The way to achieve this behaviour in the current version of autocomplete is to set the autoHighlight prop to true this will autoHighlight the first entry in the drop down list and allow you to select it using enter.
Using autoHighlight seems to improve the situation, but doesn't fix it since you can still escape the list and hit enter, which changes the value with the reason "createOption", which I don't understand because it's letting me create an option I already have, which is a catalyst for bugs, since it's easy to get the duplicate tag error (multiple autocomplete) this way.
We are using AutoComplete with filtering for selecting options from hundreds of items. But when we specify filter and only one option is visible in suggestions, pressing enter should allow to select it (trigger onNewRequest with this item). Now user have to use keydown to select option and then press enter to select the option. It is a little annoying, especially that using keydown with AutoComplete and openOnFocus is problematic as described in #4922
I know that it can break some functionality with selecting values not listed. But connecting this feature with #5494 can give a great user experience.
Link to minimal working code that reproduces the issue
http://www.material-ui.com/#/components/auto-complete
Versions
The text was updated successfully, but these errors were encountered: