• Please post questions to the jQuery discussion list, putting [autocomplete] into the subject of your post, making it easier to spot it and respond quickly.
• Please post bug reports and other contributions (enhancements, features) to the jQuery bug tracker (requires registration). Please put [autocomplete] into the title of a ticket.

@Brian: Thats fixed in 1.0.

@Jiming: So you want just the list, without any filtering? Whats the point of a replacing a select then?

@dineshv: Setting up json-powered autocomplete is possible and there are several json-examples in the demo. More to come.

@Sean: You should pass that county-data as a parameter, using the extraParams-options. It accepts a callback as parameters, so you just have to specify a function that returns the current county-value.

@Alex: Same as above, use extraParams with functions as the value.

@solot: Yes, it is, with the limitation that values can be added only at the end of the input. Take a look at the multiple-option and related examples in the demo.

@Andrea: Yes, that is a bug. Thanks for reporting, I’ll take a look.

@jiangti: Yes, via the matchContains-option.

@brad vincent: The first issue is fixed. The second is intended behaviour, allowing you to navigate to the end of the list very fast, or back up to the top.

@Dayberry: I’m working on a solution to improve tab-handling.

@Prem: The code is dual-licensed under MIT and GPL, like jQuery itself. Donations (via Paypal) are welcome.

@John: Use the setOptions method.

@Hesham: The focus/blur issue has top priority. Its in place to avoid the even more annoying issue of accidentally submitting the form.

@Wim Leers: Thanks for confirming the issue and providing example code. I’ll try to fix the issue.

@Raja: You could leverage jQuery’s global ajax events to track requests. They all provide the settings that are passed to $.ajax as an argument, so you could match autocomplete requests via settings.url.

@theintoy: Thats an interesting problem of unintended usage. I’ll have to give it a try to see how a workaround could look like. A testpage would help.

@Tuyra POL: What exacetly is the issue?

@Rogers Hellman: Yes, using the result(Function )-method.

@al_shopov: Thanks, fixed.

@graeme d: Wrap the value in a function which returns it, it’ll get called before sending the request.

@Piotr Gabryjeluk: Thanks for the pointer, fixed in latest revision.

@al_shopov: Tickets are preferred for specific requests.

@Gideon: Fixed in 1.0 release.

@Markus: Currently not supported.

@Allan Kikkas: Fixed in 1.0 release.

@mansoft: I’ve successfully used the plugin with german umlauts, yes. Its mostly a matter of the server sending the right encoding – where UTF-8 yields the most reliable results.

@xyz: That fix is now part of the 1.0 release.

@Engels: That issue is fixed in the 1.0 release. Now only the ACTIVE class gets removed on scrolling.

@andreas: Thanks, fixed!

I was just on here and thought I *might* be able to help.

Here’s something I use:

$("#driverName").autocomplete("../ajax/DriverSearch.php", {
delay: 150, minChars: 3, width: 336, max: 10, matchSubset: false, scroll: false,
formatItem: function (row){
return "" + row[0] + "" +
"" + row[2] + "";},
formatResult: function (row){return row[0] + "...transferring...";}
});
$("#driverName").result(function(event, data, formatted) {
$("#driverName").attr("disabled", "disabled");
document.location.href = 'DriverDisplay.php?driverID=' + data[1];
});


I’m no expert but I think it does what you’re trying to accomplish.


function formatItem(row) {
return "&lta href='" + row[0] + "'&gt" + row[1] + "&lt/a&gt";
}


Hi.

I am trying to do something that seems obvious to me, yet a little weird as nobody else seems to have asked or done it.

I have the plugin working fine, and the backend script supply all the correct data. As the lookup successfully finds what it is looking for, I am trying to make the information returned in the list http link to the found row:
e.g.

function formatItem(row) {
return "" + row[1] + "";
}

$('#ajaxsearch').autocomplete("search.php", {
width: 800,
max: 20,
formatItem: formatItem,
formatResult: formatResult
});

The information replied from the server is:
http://www.example.com/first_link.htm|First link…

The problem iis, when the user clicks the link in the list the click is consumed by the component and the href link is not followed.

How can I get this component to not consume the click and therefore enable the browser to follow the href link?