This is actually the kind of scenario I expected you to describe (and
I didn't mean to sound as snide as my "fascinated" comment looks).
It would seem to turn on the client's/users preferences and
expectations. If as Chris notes "users may NEVER use the browser/
computer for anything other than this app" then you might be best off
going with the "Enter" key option.
I would discuss with the client, and if possible a representative
user or three, the various trade offs:
Browser default behavior vs. legacy app behavior
Cost of implementation vs cost of teaching "new" user behavior
etc.
It may for instance be cheaper to retrain the existing user base than
to train each new future user, especially as it is probable that more
future users will be used to web forms in general...
Andrew
109B SE 4th Av
Gainesville
FL 32601
Cell: 352-870-6661
http://www.andrewmaben.com
[EMAIL PROTECTED]
"In a well designed user interface, the user should not need
instructions."
On Feb 27, 2007, at 1:49 PM, Nick Roper wrote:
Many thanks to all for the feedback so far. The general consensus
certainly seems to be that use of the Enter key is not a good idea,
and I totally accept the reasons put forward.
Just to clarify things a bit, this is indeed and intra/extranet
based application. In fact the project is to convert an existing
Access database application to a web-based PHP/MySQL application
that can be accessed remotely via a secure login. A few admin users
will be able to enter & update data via forms, whilst others will
be able to select/view information and reports. It would only be
the admin users that would possibly have the facility to use the
Enter key - which is what they do with the current system.
As Chris points out, the use of the Enter key is quite common in
data-centric applications (which this is) and the users are used to
using the Enter key for that purpose.
I probably should have made all this clearer in my original post.
Would the group consider the request more reasonable in these
circumstances - perhaps if it is made clear that this is non-
standard behaviour that should only be introduced on the non-public
areas, or are there still strong reasons for avoiding? If so, then
I'm quite happy to tell the client.
Nick
Chris Williams wrote:
How about the fact that many data entry programs use enter to move
between fields? It is actually quite common in very heavy data-
centric applications.
---------------------------------------------------------------------
---
*From: *Andrew Maben <[EMAIL PROTECTED]>
*Subject: *Re: [WSG] Use of Enter key to naviagte between form fields
But perhaps your customer has some convincing rationale for
wanting to do this? If so, I'm sure we'd all be fascinated to hear
it.
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
--
Nick Roper
partner
logical elements
innovative web and internet solutions
zend/php & mysql approved partner
email: [EMAIL PROTECTED]
phone: +44 1749 676798
www: www.logical.co.uk
skype: nick.roper / +44 20 7870 9587
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
