#4029 closed bug (invalid)
[autocomplete] - (bassistance.de) - IE6 & 7 on blur issue
Reported by: | richard-ward | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | 1.3.2 |
Component: | plugin | Version: | 1.3.1 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
Hi, I have noticed an issue with the jQuery autocomplete plugin from bassistance.de. The issue can be recreated on the demo site at http://jquery.bassistance.de/autocomplete/demo/
Using both IE6 and IE7 begin to type a word into the single city autocompleter and when the options appear (you need to do one where the scrollbar is showing) click on the scroll bar to scroll down. Now click off the results (do not select a result - just click away). The results will not hide...
This issue only seems to occur when clicking on the scrollbar, using the keys or mousewheel do not appear to cause the issue, just clicking.
Change History (4)
comment:1 Changed 14 years ago by
comment:2 Changed 14 years ago by
This seems to be a very similar issue to that described at http://dev.jquery.com/ticket/3773, I have added the fix mentioned on that page, and it works for the time being. It is however not perfect as two clicks away from the results are needed to achieve the required result.
comment:3 Changed 14 years ago by
To make the fix from http://dev.jquery.com/ticket/3773 work without having to select away twice, I have changed the fix to be the following:
$('body').mouseup(function() { if (config.mouseDownOnSelect) { input.focus(); config.mouseDownOnSelect = false; input.blur(); } });
if you want to have focus on the field still (personally i don't) then add another
input.focus();
after the
input.blur();
Not an ideal fix, but good enough for now!
comment:4 Changed 14 years ago by
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 .
After a short look i think the following line is the issue - I do not think it is being called in IE. (part of the init() method lines 587 - 589.