I don't quite the how the issue is related to ExtJS. It sounds like you pass functions instead of strings to the autocomplete plugin, which is the actual issue here. Could you upload a testpage and post the URL here?
Jörn On Tue, Jun 24, 2008 at 1:03 PM, Bramus! <[EMAIL PROTECTED]> wrote: > > Filed a ticket on dev.jquery including a .diff file: > http://dev.jquery.com/ticket/3080 > ;-) > > Regards, > B! > > PS: [autocomplete] prefix seems to be cut off subject? > > On Jun 24, 11:15 am, "Bramus!" <[EMAIL PROTECTED]> wrote: >> Hi Jörn et all here at the list, >> >> I'm using the autocomplete plugin in a project I'm working on and I >> must say: it works great!. However: one part of the project uses ExtJS >> (their tree component is great) and that's where things go wrong. >> Problem is that somewhere in ExtJS they extend Object with a remove() >> function, breaking jQuery.autocomplete. >> >> After a little quest I found that - quite obviously - autocomplete >> breaks on string manipulations (Function.toLowerCase() doesn't really >> exist ;)) and has a minor issue when displaying the items whenever >> some library has extended Object. >> >> Here below are the 2 minor changes I implemented in order to make >> things work "just fine" again. Could you tuck 'm into the release as I >> can't commit any changes to the trunk. >> >> Change #1: Display issue: $.Autocompleter.Select, function fillList(): >> replace: >> if (!data[i]) >> with: >> if (!data[i] || (data[i].value.constructor === Function)) >> >> Change #2: Selection issue: $.Autocompleter.Cache, function >> matchSubset() >> at line#1 of this function (directly after the opening { ) add: >> if (s.constructor === Function) return false; >> >> Regards, >> Bramus! >
