I figured this out. The problem was not with AjaxQueue it was that the abort method was not firing ajaxStop which is what I was using to hide the loading indicator. Upgrading my jquery.js file from 1.2.6 to 1.3.2 fixed this.
Thanks. On Sep 28, 11:08 am, Jörn Zaefferer <joern.zaeffe...@googlemail.com> wrote: > Can you provide a testpage? > > Jörn > > On Mon, Sep 28, 2009 at 7:59 PM, jmunning <jasonmunn...@gmail.com> wrote: > > > Anyone have any ideas about this? I'm stuck on this. > > > Thanks > > > On Sep 22, 2:47 pm, jmunning <jasonmunn...@gmail.com> wrote: > >> Hi all, > > >> I am using the bassistance autcomplete plugin version 1.1 along with > >> the bundled ajaxQueue.js file. > > >> When text is inputted into the autocomplete, it seems to be keeping > >> the ajax calls open and loading even though they never resolve -- as > >> shown by a loading indicator which is stuck and in the Firebug > >> console. It looks to me like the ajaxQueue plugin is supposed to fix > >> this but it doesn't seem to be aborting. > > >> I can't for the life of me figure out what the problem is or how to > >> resolve it. Does anyone have suggestions of what I could look for? > > >> It seems to come down to this section in ajaxQueue.js: > >> [code] > >> case "abort": > >> if ( pendingRequests[port] ) { > >> pendingRequests[port].abort(); > >> } > >> return pendingRequests[port] = ajax.apply(this, > >> arguments); > > >> [/code] > > >> If I put an if statement on the line containing the 'abort' command > >> then I can see that that command is not completing. Not sure why > >> though. > > >> Here is my code: > > >> [code] > >> $("#suggest").autocomplete('auto_data.php?table=patents', { > >> width: 557, > >> multiple: true, > >> multipleSeparator: "\n", > >> matchSubset:false, //setting this to false causes entries > >> to > >> disappear after selected > >> mustMatch: false, > >> max: 20, > >> delay: 0 > >> }); > > >> [/code] > > >> And here is the site it is running on: > >> http://www.xyggy.com > > >> Thanks for any help.