|
|
Posted by Jukka K. Korpela on 04/27/07 13:54
Scripsit Travis Newbury:
> On Apr 26, 1:08 pm, Leif K-Brooks <eurl...@ecritters.biz> wrote:
>
>> That's standard, expected functionality. When an even slightly
>> clueful user presses the enter key in a form, they want to submit
>> it. Don't make that more difficult.
>
> I HATE that functionality! I want to click a button to submit the
> form, if I press the enter key, I want it to do a carriage return or
> nothing.
So whenever you use Google, you want type in the search string, then look
for the mouse and try to click on the submit button, instead of pressing the
enter key (with no need for a mouse for this simple operation)?
What does a carriage return do in a single-line input field?
I have sympathy for your sentiments as regards to large forms, especially
forms with handlers that aren't prepared to handling incomplete submissions.
But the feature itself is very useful and natural and it was even described
as suggested behavior in early HTML specifications - for a form with a
single input field (optionally with checkboxes and radio buttons, but no
other fields for text input). Some browsers then implemented it for _all_
forms, and here we are.
It might be a good idea to disable the enter key in large forms, to the
extent possible, but it is important to realize that it cannot be completely
disabled and users _will_ submit data that is not all they meant to send, so
they should be given a chance to complete the form when the handler detects
the situation.
--
Jukka K. Korpela ("Yucca")
http://www.cs.tut.fi/~jkorpela/
Navigation:
[Reply to this message]
|