#9334 closed bug (fixed)
Autocomplete: Multiple instances should be able to start asynchronous requests simultaneously
| Reported by: | paftek38 | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | 1.10.4 |
| Component: | ui.autocomplete | Version: | 1.10.3 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
Actually two autocomplete instances are not able to start asynchronous requests simultaneously because of the global "requestIndex" variable used to prevent race conditions.
Both dropdowns should be displayed, but the response of the first autocomplete is being dropped: http://jsbin.com/ekakez/5
"requestIndex" should not be global but instance relative.
Change History (5)
comment:1 Changed 10 years ago by
| Status: | new → open |
|---|---|
| Summary: | Two autocomplete instances should be able to start asynchronous requests simultaneously → Autocomplete: Multiple instances should be able to start asynchronous requests simultaneously |
comment:2 Changed 10 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | open → closed |
comment:3 Changed 10 years ago by
| Milestone: | none → 1.11.0 |
|---|
comment:4 Changed 9 years ago by
Autocomplete: Scope race condition handling to the instance. Fixes #9334 - Autocomplete: Multiple instances should be able to start asynchronous requests simultaneously. (cherry picked from commit 9e00e00f3b54770faa0291d6ee6fc1dcbad028cb)
Changeset: e4a194ce42b8ea1e5440f99d1d8d26f55526ff6c
comment:5 Changed 9 years ago by
| Milestone: | 1.11.0 → 1.10.4 |
|---|
Note: See
TracTickets for help on using
tickets.
Autocomplete: Scope race condition handling to the instance. Fixes #9334 - Autocomplete: Multiple instances should be able to start asynchronous requests simultaneously.