matchResponseProperty incorrect asynchronous responses shown

[DanHarltey]

Hi,

I have started using the autocomplete on my new site and I have found a problem where the incorrect results for the entered search term are shown. The matchResponseProperty does not correctly work. The issue can be recreated by making two remote requests for data and having the first request response after the second. For example make two requests for "Tes" and "Test", if "Test" responses first the autocomplete will show the correct results. However when the response for "Tes" arrives after, these results are shown, this is incorrect as the input box contains "Test". This issue particularly affects mobile connections with slow connections.

The error comes about because the inputPhrase is captured before the ajax request and is not reread from the input box on the ajax response. I have replaced this functionality with a simple counter "remoteRequestCount". The counter is captured into a local variable and then rechecked against the state. This also has the befits of not having the users having to include matchResponseProperty in there servers response.

I am sorry but I have only altered the source files. I am an expired developer but not in the javascript world and could not get my grunt build going in the time I had.

Thank you
Dan

[fadhilkurnia]

I am also facing this bug, I think it is better if EasyAutoComplete can cancel previous requests, if another request is created. Just like this library: http://autocomplete-js.com/