On 4/27/09 5:25 AM, "Matthew Vickery" <vickery.matt...@gmail.com> wrote:
> Thanks for your reply. I see what you mean about the tab key... I hope > someone offers you some advice so you can use the plugin without branching. i already have an auto-completion of my own that i wrote a few years ago before i knew of jquery. it requires only about 10% of the locs that autocomplete plugin uses because it only does what i need and not all that other stuff too. rewriting my code for the new app (maybe using jq) is perhaps less work than maintaining my own version of the plugin. i'm willing to take a bet on jq being around and supported in future. i'm not sure about autocomplete. > If you do find a solution I'd be glad to hear it too. Did you see my > response re; 'selectFirst: false' ? I don't know if this would help your > problem but it solved mine. it helps but it's not enough. for an example with "selectFirst: false": 1. go to http://jquery.bassistance.de/autocomplete/demo/ 2. click in the "Single Bird (remote):" text input. 3. type, say, "pal" and wait for the suggestions to appear. 4. hit tab. in my browser, the "Get Value" button focuses for a moment then the focus moves back to the "Single Bird (remote):" text input. it takes two tabs to get the focus out of there. that really runs against user expectations and makes no sense. for people used to working fast through forms with the keyboard only, this behavior will be inexplicable and annoying.
