Side navigation
#4292 closed bug (invalid)
Opened March 04, 2009 08:46PM UTC
Closed October 12, 2009 11:59PM UTC
[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: | |
| Blocked by: | Blocking: |
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.)
Attachments (0)
Change History (2)
Changed March 04, 2009 09:08PM UTC by comment:1
Changed October 12, 2009 11:59PM UTC by comment:2
| resolution: | → invalid |
|---|---|
| status: | new → closed |
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 .
Forgot to mention unautocomplete() works correctly with jQuery 1.2.6 (which is the version the plugin was deployed with)