That is a very good point Bryan.  I will test this script with onKeyPress as
well, but not for this instance.  The reason that I needed this script in
the first place is the fact that the end user for this particular app has no
'gut reaction' as you call it.  They don't know that you can easily get to
the next field with the Tab key, and I was just in pain when I watched them
testing it yesterday typing in 2 characters, going to the mouse, aiming, and
clicking, rinsing and repeating.

:P

<insert random derogatory comment about end users here>

-----Original Message-----
From: Bryan LaPlante [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 01, 2001 10:37 AM
To: [EMAIL PROTECTED]
Subject: Re: [KCFusion] JavaScript question


One quick thing to mention is that using the onkeyup event calls autoTab at
a moment when the users gut reaction is to hit the tab key resulting in
focus to the third element when the second element in the chain was the
desired next element to be filled in. Use onkeypress and the user will be
tabbed to the next form element when they mistakenly do not hit the tab key
at the correct time.

My 2 cents
 
 
______________________________________________________________________
The KCFusion.org list and website is hosted by Humankind Systems, Inc.
List Archives........ http://www.mail-archive.com/cf-list@kcfusion.org
Questions, Comments or Glowing Praise.. mailto:[EMAIL PROTECTED]
To Subscribe.................... mailto:[EMAIL PROTECTED]
To Unsubscribe................ mailto:[EMAIL PROTECTED]
 

Reply via email to