[jQuery] Re: [autocomplete] Search Page Replacement

2009-05-10 Thread Tom Worster
On 5/8/09 3:36 PM, "Logan Green" wrote: > This tab issue is driving me crazy. Has anyone found a hack/fix that > will allow the tab to work as expected...where the user hits tab once, > and moves to the next field? not that i am aware of. given the activity on this plugin (it's been nearly a

[jQuery] Re: [autocomplete] Search Page Replacement

2009-05-08 Thread Logan Green
This tab issue is driving me crazy. Has anyone found a hack/fix that will allow the tab to work as expected...where the user hits tab once, and moves to the next field? On Apr 27, 5:49 am, Tom Worster wrote: > On 4/27/09 5:25 AM, "Matthew Vickery" wrote: > > > Thanks for your reply.  I see wha

[jQuery] Re: [autocomplete] Search Page Replacement

2009-04-27 Thread Tom Worster
On 4/27/09 5:25 AM, "Matthew Vickery" 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.

[jQuery] Re: [autocomplete] Search Page Replacement

2009-04-27 Thread Tom Worster
On 4/26/09 9:31 PM, "Jordon Bedwell" wrote: >> this is one of two counter-intuitive keyboard behaviors i'm aware of. the >> other is tab, which most users would expect to get them to the next form >> element. > > I'm still scratching my head at how this is counter-intuitive? If you called > it

[jQuery] Re: [autocomplete] Search Page Replacement

2009-04-27 Thread Matthew Vickery
Hi Tom, 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 yo

[jQuery] Re: [autocomplete] Search Page Replacement

2009-04-26 Thread Jordon Bedwell
bject: [jQuery] Re: [autocomplete] Search Page Replacement >this is one of two counter-intuitive keyboard behaviors i'm aware of. the >other is tab, which most users would expect to get them to the next form >element. I'm still scratching my head at how this is counter-intuitive? If

[jQuery] Re: [autocomplete] Search Page Replacement

2009-04-26 Thread Jordon Bedwell
>this is one of two counter-intuitive keyboard behaviors i'm aware of. the >other is tab, which most users would expect to get them to the next form >element. I'm still scratching my head at how this is counter-intuitive? If you called it that, you must not understand the entire scope of tab, and

[jQuery] Re: [autocomplete] Search Page Replacement

2009-04-26 Thread Tom Worster
On 4/26/09 9:12 AM, "mattvick" wrote: > 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