Opened 5 years ago

Closed 5 years ago

#1485742 closed Feature Patches (duplicate)

Autocomplete asynchronous LDAP queries conflict each other

Reported by: Erika Owned by:
Priority: 3 Milestone: 0.2.1
Component: LDAP connection Version: 0.2-stable
Severity: major Keywords: ldap autocomplete


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...

Change History (2)

comment:1 Changed 5 years ago by Erika

Please see Ticket #1485743 - and delete this one if you can...:-)

comment:2 Changed 5 years ago by alec

  • Resolution set to duplicate
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.