Skip to main content

Search and Top Navigation

#10121 closed bug (notabug)

Opened June 21, 2014 09:01PM UTC

Closed June 22, 2014 12:21AM UTC

Autocomplete: `pending` count does not get reset with remote source in some cases.

Reported by: jessehouchins Owned by:
Priority: minor Milestone: none
Component: ui.autocomplete Version: 1.10.4
Keywords: Cc:
Blocked by: Blocking:

This seems identical to this bug that was apparently fixed in 1.8: However I am still seeing it in v1.10.4

My specific case is as follows.

1. I have a remote source function.

2. if I type a search quickly and tab out before results return, the ui-autocomplete-loading class remains. Removing this class manually and performing another search still leaves the class (assuming that the pending counter is not returning to zero.

Attachments (0)
Change History (2)

Changed June 21, 2014 09:20PM UTC by jessehouchins comment:1

It seems like this is actually a problem with my source function implementation. I was debouncing my source function manually rather than using the delay option so i could trigger the search event immediately. This meant that not all autocomplete._search calls were creating a ._response call. This can be closed.

Changed June 22, 2014 12:21AM UTC by scottgonzalez comment:2

resolution: → notabug
status: newclosed