Has there been consideration of using the autocomplete plugin here http://plugins.jquery.com/project/jq-autocomplete by ReinH/wycats? Or its updated version here http://github.com/ReinH/jquery-autocomplete/tree/master? It's extremely lightweight (3Kb) and simple to use, especially when used in conjunction with the templating plugin.
On Oct 10, 6:08 am, "Jörn Zaefferer" <[EMAIL PROTECTED]> wrote: > Thanks for your feedback, I'm currently gathering the various > suggestions. The bugtracker should be back up soon, so we can organize > it there. > > Jörn > > On Thu, Oct 9, 2008 at 2:40 PM, Jason Tackaberry <[EMAIL PROTECTED]> wrote: > > > [I sent this message via email to [email protected], but it > > seems to have been sucked into some Google black hole. On the off > > chance it makes it through anyway, I apologize in advance for the > > dupe.] > > > I understand that Autocomplete will not be included in 1.6. > > Autocomplete is indeed fairly quirky. It's probably a good idea to > > defer it to 1.7. But it's an exceedingly useful plugin, IMO. I do > > have > > some feedback: > > > Firstly, on Firefox, holding the up/down arrows in the popup menu does > > not continue to select items up or down the menu. The following code > > (which I've reformatted in anticipation that this google groups > > webform would mangle it) is > > the culprit: > > > // only opera doesn't trigger keydown multiple times while > > // pressed, others don't work with keypress at all > > $input.bind(($.browser.opera ? "keypress" : "keydown") > > + ".autocomplete", function(event) { > > > This is somewhat dubious. For a previous project, I actually > > developed > > an autocomplete widget similar to the one in jQuery UI, and had faced > > this issue. I came to entirely different conclusions. From my code: > > > // Firefox doesn't fire multiple keydown events when keys are > > held, > > // whereas IE does. But IE doesn't fire keypress events for arrow > > // keys. So we use 'keydown' for IE, and 'keypress' otherwise. > > var key_event = $.browser.msie ? 'keydown' : 'keypress'; > > > When I change the jQuery UI autocomplete code to match this logic, it > > seems to work with no ill effects. (This works with Opera as well, > > but > > I have not tested Safari.) > > > Secondly, changing any options added to this.options in the _init() > > function does not work. These options are, specifically, delay, max, > > highlight, and formatMatch. That is to say, if I do ... > > > $('input').autocomplete({ > > url: '/someurl', > > max: 25, > > delay: 100 > > }) > > > ... delay is still 400 (the URL is not hit until 400ms after typing), > > and max is still 150 (the limit variable in the GET request is 150). > > > Thirdly, I would very much like separate behaviour for TAB and RETURN. > > Currently you can either enable selectFirst for both, or disable for > > both. I would like TAB to select first, but RETURN _not_ to. In > > fact, > > I see this as the sanest default setting, too. > > > Thanks for all your hard work on jQuery UI! > > > Cheers, > > Jason. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jQuery UI" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/jquery-ui?hl=en -~----------~----~----~----~------~----~------~--~---
