Autocomplete asynchronous LDAP queries conflict each other
|Reported by:||Erika||Owned by:|
Multiple autocomplete queries ('a', then 'ab' for example) are not received in the exact order they have been sent.
That leads to a conflict when 'a' query is received after 'ab' query (faster than 'a' one).
The following patch makes the query results not being displayed, when they are related to a different searched word than the current input value.
The best would have been to be able to cancel the HTTP autocomplete request, but I don't know any way to do it...