Skip to main content

Search and Top Navigation

#5982 closed bug (fixed)

Opened August 23, 2010 08:28PM UTC

Closed August 24, 2010 01:15PM UTC

Last modified November 19, 2010 06:26PM UTC

Autocomplete: Race condition causes incorrect suggestions

Reported by: cardmeister Owned by:
Priority: minor Milestone: 1.8.5
Component: ui.autocomplete Version: 1.8.4
Keywords: Cc:
Blocked by: Blocking:
Description

This condition occurs when using a remote data source and is described by the following sequence:

(Note, "termA" and "termB" in this description are simply placeholders for any valid search term.)

1) User input meets minLength and delay requirements and search for termA begins.

2) Before results for termA are returned, user continues typing and triggers another search for termB.

3) termB results are returned while termA results are still pending.

4) termB results are displayed (as expected)

5) termA results are returned, and are displayed. User now has incorrect suggestions displayed.

This is easiest replicated by a using a back-end script which creates an artificially long delay for termA.

Attachments (0)
Change History (3)

Changed August 24, 2010 01:15PM UTC by scottgonzalez comment:1

milestone: TBD1.9
resolution: → fixed
status: newclosed
summary: Race Condition causes incorrect suggestionsAutocomplete: Race condition causes incorrect suggestions

Fixed in f115b48.

Changed September 10, 2010 05:28PM UTC by scottgonzalez comment:2

milestone: 1.91.8.5

Changed November 19, 2010 06:26PM UTC by Scott González comment:3

Autocomplete: Don't handle remote data if it's not the most recent request. Fixes #5982 - Autocomplete: Race condition causes incorrect suggestions.

Changeset: f115b48d2bd79aff1f65fb895d1ebc9517d82edc