Search and Top Navigation
#9334 closed bug (fixed)
Opened May 28, 2013 02:00PM UTC
Closed May 28, 2013 03:05PM UTC
Last modified November 26, 2013 03:36PM UTC
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:
"requestIndex" should not be global but instance relative.
Attachments (0)
Change History (5)
Changed May 28, 2013 02:07PM UTC by comment:1
| 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 |
Changed May 28, 2013 03:05PM UTC by comment:2
| resolution: | → fixed |
|---|---|
| status: | open → closed |
Autocomplete: Scope race condition handling to the instance. Fixes #9334 - Autocomplete: Multiple instances should be able to start asynchronous requests simultaneously.
Changeset: 9e00e00f3b54770faa0291d6ee6fc1dcbad028cb
Changed May 28, 2013 03:05PM UTC by comment:3
| milestone: | none → 1.11.0 |
|---|
Changed November 26, 2013 03:34PM UTC by comment:4
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
Changed November 26, 2013 03:36PM UTC by comment:5
| milestone: | 1.11.0 → 1.10.4 |
|---|