Skip to content
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

Unexpected focus of AutoComplete's first search result item with slow filter requests and highlightFirst false #3852

Closed
Juveniel opened this issue Dec 14, 2017 · 4 comments
Assignees
Labels
Milestone

Comments

@Juveniel
Copy link
Contributor

Juveniel commented Dec 14, 2017

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

  1. Run the following Dojo example or the Server Filtering demo
  2. Click on the AutoComplete and type gran - Grandma's Boysenberry Spread is filtered
  3. Blur the AutoComplete
  4. 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.
  5. Click on the AutoComplete after gran and type d - this triggers a filter request.
  6. 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.

Screencast

Expected/desired behavior

The first option of the list should not be focused when highlightFirst option is set to false.

Environment

  • Kendo UI version: 2021.2.511
  • Browser: all
@jignesh-dalal
Copy link

I think this matches with the issue #4428 that I filed. Please see Workaround section for a possible fix.

@Iankodj Iankodj added the Triaged label Oct 9, 2018
@Juveniel 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 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
@Dimitar-Goshev
Copy link
Contributor

Dimitar-Goshev commented 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)"

@dmitriy-barkalov
Copy link

Hi Team, please share if there is a plan to fix the issue.

@nelito987
Copy link
Contributor

Reported in ticket id: 1567327

@gdenchevprog gdenchevprog self-assigned this Dec 7, 2023
@github-actions github-actions bot added the FP: Completed Sync status with associated Feedback Item label Jan 15, 2024
@sspasova sspasova added this to the 2024 Q1 milestone Jan 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

9 participants