I don't believe using tab to iterate through an auto-complete list would be the expected behavior. In my opinion, an auto-complete list should mirror the behavior of a regular select element, whereby hitting tab would select the currently high-lighted list option and move to the next form field. Anything else would seem disjointed to the user. What key would get you to the next field? Enter, and _then_ tab? That's an unnecesary step considering you'd have to use the up-arrow to go backwards in the list anyway. If you are already going to use one arrow why not use them both?
-khoker On Apr 12, 12:32 am, Klaus Hartl <[EMAIL PROTECTED]> wrote: > Jörn Zaefferer schrieb: > > > > > Hi folks, > > > I've achieved some progress on the autocomplte plugin. The features > > added by Dan Switzer to Dylan's initial plugin are now merged with > > modifications for completing multiple values, like in the gmail > > recpient-field. > > > I made some minor API changes, changed a lot of default values to > > provide nice behaviour without specifying any options and refactored > > quite a lot of code to be able to fix the bugs I most likely introduced. > > I switched to event delegation for the select box, possibly improving > > performance a bit. Though Dylan's and Dan's caching code is already > > providing fast-as-hell autocompletition. > > > There is one major issue I want to solve before publishing a first > > release of that rewrite. Until then the code can be found in jQuery's > > repository[1], if anyone is interested in testing: You're welcome! > > > [1] svn://jquery.com/trunk/plugins/autocomplete > > Jörn, thanks for this. One question: I once modified Dylan's > autocomplete a bit, so that if the autocomplete list is shown, tabbing > would tab through the list instead of to the next form element. Is it > possible to take into account? > > Have a look here:http://plazes.com/plazesand type something into the > "Where" field. > > I think I also modified the behavior for arrow up/down keys a bit... > > -- Klaus
