As I understand the control, you type a search term and requests are fired with the queried search term grouped by the speed you type, i.e. type fast and you get one request for the whole term or type slowly and get one request for each character.
If you type really fast, there is no issue. And if you type really slowly allowing the request to complete and update the results on screen before typing the next character, there is also no issue. However, type like you only use one finger (allowing a request to start but not complete before you type the next character) and we have problems. It would appear that only the first request fired is respected in the results and it will not update again unless you type another character, i,e, type 1...5...0 and only see the results for '1', then type 0 and get the results for '1500', what happened to the results for '150'?
I have been through the documentation and forums and this appears to have been an issue for sometime, below are a couple of the closest forum posts - from 2013!
- http://www.telerik.com/forums/abort-previous-requests-on-keypress
- http://www.telerik.com/forums/webservicesettings-delay-issue-handling-of-requests-in-order
Was this issue ever resolved?
1 Answer, 1 is accepted
The issue you observe is caused by the interaction request delay that we add in order to get the results correctly. We have made a lot of testing and it is set to 250 milliseconds by default. Yet in custom cases as the one that you described if the request is a little bit slower or faster this delay may need update according to the scenario. That is why we recommend setting the _requestDelay to a different value according to your case as my colleague explained here.
Hope this will explain the issue and help you solve it.
Regards,
Plamen
Telerik