Shelane,
thanks for your reports! That helps a lot. In detail:
I believe I found a bug in the new autocompleter. Line 157 has:
var $input = $(input).attr("autocomplete",
"off").addClass(options.inputClass);
Good catch, fixed.
If the default caching is set at 10 and matcheSubset default is true, why is
it making a second call to the server when I add a new letter.
First input: cap
Additional letter: i
Then a new query goes out to the server:
http://education.llnl.gov/jQuery/pages/lookup.lasso?q=capi&limit=50
That isn't supposed to happen, I'll need to check that.
Second question: is there a way I can do max all? It seems counter
intuitive if caching is used. Unless it's set so that if caching is used,
only the final output is limited.
Third question: I have seen a few examples out there including these params:
highlight: false,
highlight: function(value) {
//alert(value);
return value;
},
But I don't see anything documenting these (in your documentation online).
I haven't made a new release yet. To keep up-to-date with the latest
revision you can get it directly from the repository:
http://dev.jquery.com/browser/trunk/plugins/autocomplete/jquery.autocomplete.js?format=txt
The updated documentation is already there, but not very readable.
Forgot to add my example link:
http://education.llnl.gov/jQuery/ajax.html
Click auto complete (unknown if this is working at all in IE right now).
Definitely in FF. Your plugin is the second example.
You may want to set the width of the displayed select box via the width
option. That should help to avoid line breaks within one item.
Let me know if you notice anything else!
--
Jörn Zaefferer
http://bassistance.de
