Behavior of the autocomplete component is a bit confusing. When user clicks out of the input or scrolls page, the value in the input is reset. I find it especially confusing with fetched options, as the following scenario might happen:
User types a value to input.
Options are fetched based on the value.
User scrolls page.
Input value is reset, but the options stay the same, as the function that is fetching options usually doesn't do so if the value is empty string*.
Type "Pr" into the Single search autocomplete with fetched options list autocomplete.
Scroll the page or click somewhere out of the input.
Click on the input.
Options stays set to "Prague" as this is the only option satisfying the "Pr" string, but the "Pr" string is not in the input anymore.
*The solution might be to simply reset options when the input value is empty string instead of returning and doing nothing, but I still find resetting input value on scroll/on blur unexpected.
Behavior of the autocomplete component is a bit confusing. When user clicks out of the input or scrolls page, the value in the input is reset. I find it especially confusing with fetched options, as the following scenario might happen:
How to reproduce.
Single search autocomplete with fetched options listautocomplete.*The solution might be to simply reset options when the input value is empty string instead of returning and doing nothing, but I still find resetting input value on scroll/on blur unexpected.