Ticket #4292 (closed bug: invalid)
[autocomplete] unautocomplete does not work properly with jQuery 1.3.2
| Reported by: | till | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | 1.3.2 |
| Component: | plugin | Version: | 1.3.2 |
| Keywords: | autocomplete, bassistance, plugin, unbind | Cc: | |
| Blocking: | Blocked by: |
Description
The unautocomplete method does not work correctly in latest autocomplete plugin 1.0.2 with jQuery 1.3.2
unautocomplete() should remove all autocomplete functionality from a jQuery object. The problem is that apparently jQuery's unbind() without parameters does not unbind the plugin's keydown handler. This results in multiple keydown handler calls, if one binds another autocomplete afterwards (of the previous binded autocompletes as well as from the current new one).
Fix would be to do this specifically. In jquery.autocomplete.js line #196 the generic $input.unbind(); is done; before that a $input.unbind("keydown.autocomplete"); is needed.
(This might be a jQuery bug.)
Change History
comment:3 Changed 4 years ago by dmethvin
- Status changed from new to closed
- Resolution set to invalid
This is not a jQuery core bug. Please report plugin bugs to the plugin's author, or ask on the jQuery forums. jQuery UI bugs should be reported on the UI bug tracker, http://dev.jqueryui.com .
Please follow the bug reporting guidlines and use jsFiddle when providing test cases and demonstrations instead of pasting the code in the ticket.
Forgot to mention unautocomplete() works correctly with jQuery 1.2.6 (which is the version the plugin was deployed with)