enhanceSelectElement always sets autoselect to true
See original GitHub issueopts.autoselect = opts.autoselect || true
should be
if (opts.autoselect === undefined) opts.autoselect = true
I think
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Stop saving the latest valid choice · Issue #432 - GitHub
Question: How can we ensure that the enhanceSelectElement always treats what is in the input field as the desired value to submit (regardless...
Read more >Accessible Autocomplete examples
{ autoselect: true } When autocomplete results are available use up and down arrows to review and enter to select. Touch device users,...
Read more >PrimeNG AutoComplete: ForceSelection is set to true in ...
I am using Prime NG autocomplete and my expectation is that if the input is not from the suggestions it should clear on...
Read more >Basic configuration options | Autocomplete - Algolia
Use debug: true to keep the autocomplete panel open even when the blur event occurs (see Debugging).
Read more >react-select-prototype.patch - Drupal
onClearIndicatorTouchEnd,"aria-hidden":"true"};return L.a.createElement(e,Object(N["a"])({},t ... n||"set"in n)throw TypeError("Accessors not supported!
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Reasoning:
We’re setting the default to the most sensible option in each case. For enhanced inputs we need users to be able to type anything, and not have to pick from the list. For selects, users must pick from the list. So the most sensible option is different for each.
The challenge here is to have consistent options, but also an easy way for us to provide ‘recommended’ sets of options. So far we’ve done this by having defaults that offer our recommended options.
My concern with changing this default is that we’ll see most users of this component not using autoselect- a feature we’ve found to be very beneficial. I’m very open to alternate suggestions that achieve this though, and agree the inconsistency is awkward.
this was fixed by #167