Search and Top Navigation
#7603 closed enhancement (wontfix)
Opened August 04, 2011 01:04AM UTC
Closed August 04, 2011 04:49PM UTC
Last modified January 17, 2012 11:31PM UTC
Autocomplete: support canceling a search in progress
| Reported by: | ossareh | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | 1.9.0 |
| Component: | ui.autocomplete | Version: | 1.8.15 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
being able to cancel a search, and the subsequent visual events (displaying the selector, etc), permits more flexibility in how and where this widget can be used.
I have a fix that I'll sending a pull request for imminently.
Attachments (0)
Change History (7)
Changed August 04, 2011 01:12AM UTC by comment:1
| milestone: | 1.9 → 1.later |
|---|---|
| version: | git → 1.8.15 |
Changed August 04, 2011 03:38AM UTC by comment:2
Right now it works with custom sources that are urls. I'm not sure about for functions and arrays. I expect in the case of arrays this is unlikely to make any sense. Perhaps changing the name to stopAjaxRequest would be better? Also, as per the github comment - I should make this a public API.
Changed August 04, 2011 12:08PM UTC by comment:3
By custom I only mean functions. The widget does 100% of the handling for strings and arrays, so there's no custom functionality defined by the user.
My comment on GitHub wasn't that you should make this a public API, it was that there's no benefit to you by having this in the core of the widget. It's just as easy for you to add a single method in an extension. Please start a discussion on the forum if you really feel like this needs to be in the core of the widget.
Changed August 04, 2011 04:34PM UTC by comment:4
Aha, OK, I get it now. Thanks for your feedback scott.
Changed August 04, 2011 04:35PM UTC by comment:5
It seems I cannot close this ticket.
Changed August 04, 2011 04:49PM UTC by comment:6
| resolution: | → wontfix |
|---|---|
| status: | new → closed |
Changed January 17, 2012 11:31PM UTC by comment:7
| milestone: | 1.later → 1.9 |
|---|
How would this work with custom sources?