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
The AutoComplete first option is focused incorrectly, when filter requests to the server are slow, although highlightFirst is set to false. Note that its default value is also false.
Click on the AutoComplete and type gran - Grandma's Boysenberry Spread is filtered
Blur the AutoComplete
Set browser throttling (3G Slow) to simulate slow connection speed, which makes reproduction easier. Keep dev tools on Network tab to observe the filter requests.
Click on the AutoComplete after gran and type d - this triggers a filter request.
While the above filter request is still in progress, immediately after typing d press backspace to delete d - this triggers another filter request.
Current behavior
When the first filter request completes, Grandma's Boysenberry Spread is filtered in the search results.
And then when the second filter request completes, Grandma's Boysenberry Spread becomes focused, although highlightFirst is false.
Note that when the item is highlighted, pressing Tab to blur the component selects the item in the AutoComplete.
Juveniel
changed the title
highlightFirst option is triggered with slow filter requests
HighlightFirst option is triggered with slow filter requests
Nov 20, 2018
Dimitar-Goshev
changed the title
HighlightFirst option is triggered with slow filter requests
Unexpected focus of AutoComplete's first search result item with slow filter requests and highlightFirst false
Jun 2, 2021
Increasing priority - reported in #4428 and #6443 . When addressing the issue, check the related issues for additional scenarios, if needed.
In #6443 the author added the following comment, which may be useful:
"I have debugged and found that open flag still false when it must be true to remove focus of first item. (probably race condition cause asynchronous operations)"
Bug report
The AutoComplete first option is focused incorrectly, when filter requests to the server are slow, although highlightFirst is set to false. Note that its default value is also false.
Reproduction of the problem
Reproduction video
gran
- Grandma's Boysenberry Spread is filteredgran
and typed
- this triggers a filter request.d
pressbackspace
to delete d - this triggers another filter request.Current behavior
When the first filter request completes, Grandma's Boysenberry Spread is filtered in the search results.
And then when the second filter request completes, Grandma's Boysenberry Spread becomes focused, although highlightFirst is false.
Note that when the item is highlighted, pressing Tab to blur the component selects the item in the AutoComplete.
Screencast
Expected/desired behavior
The first option of the list should not be focused when highlightFirst option is set to false.
Environment
The text was updated successfully, but these errors were encountered: