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. 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. Also I found a list of all the autocomplete options here:
(Click the 'options' tab to the right of the 'overview' tab. The 'options' link further down goes somewhere else.)
Regards,
Matthew
2009/4/27 Tom Worster <fsb@thefsb.org>
On 4/26/09 9:12 AM, "mattvick" <vickery.matthew@gmail.com> wrote:this is one of two counter-intuitive keyboard behaviors i'm aware of. the
> I need the list of results to appear without any of them highlighted
> so hitting the return key submits the form without updating the text
> in the search field. I still need the search field to update, and the
> form submit, if any of the results in the list are highlighted and
> clicked manually.
other is tab, which most users would expect to get them to the next form
element.
i don't know for sure but i suspect that in most cases, changing the
> Will someone please point me in the right direction or even better
> post an example so others can also benefit.
autocomplete keystroke behaviors requires changing the plugin code.
which is a bit of a problem. i'd really like to use autocomplete in my app
but without support (the author hasn't answered any email about autocomplete
this month, afaict), seems like making it behave in a way that users won't
complain about is going to mean branching.
--
Email: vickery.matthew@gmail.com
Land line: +44 (0)20 8123 3798
No comments:
Post a Comment