#7603 closed enhancement (wontfix)
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.
Change History (7)
comment:1 Changed 11 years ago by
Milestone: | 1.9 → 1.later |
---|---|
Version: | git → 1.8.15 |
comment:2 Changed 11 years ago by
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.
comment:3 Changed 11 years ago by
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.
comment:6 Changed 11 years ago by
Resolution: | → wontfix |
---|---|
Status: | new → closed |
comment:7 Changed 11 years ago by
Milestone: | 1.later → 1.9 |
---|
How would this work with custom sources?