Jörn,
I believe I found a bug in the new autocompleter. Line 157 has:
var $input = $(input).attr("autocomplete",
"off").addClass(options.inputClass);
This throws a javascript error if jQuery.noConflict() has been called:
$(input).attr is not a function
changing it to var $input = jQuery(input).attr("autocomplete",
"off").addClass(options.inputClass);
fixes the problem
On Apr 19, 11:08 am, Jörn Zaefferer <[EMAIL PROTECTED]> wrote:
> Dan G. Switzer, II schrieb:>> What would be passed to the function? The
> containing li? a jQuery object
> >> containing the containing li? The HTML text?
>
> > The source is available here:
> >http://dev.jquery.com/browser/trunk/plugins/autocomplete/jquery.autoc...
> > .js
>
> > [...]
>
> > At the moment it runs against li.innerHTML.
>
> So far it was internal only, I'd pass the formatted string as the first
> argument and the other stuff in addition.
> Formatting would be very flexible then. Default takes a simple string
> and adds simple highlighting. Then you can replace that simple string
> with some custom formatting and default highlighting. Or you use
> formatting and include highlighting and switch off default
> highlighting... I hope we really need that degree.
>
> Ah, and thanks Dan for the regex and the link, I'll test that.
>
> --
> Jörn Zaefferer
>
> http://bassistance.de
