|
|
Posted by goliathuy on 08/09/06 13:52
Maybe you can use a confirm like:
<input type="reset" name="reset" value="Reset"
onClick="if(!confirm('REALY CLEAR THE FORM???'))return
false;"
>
on the reset buton so it can't be an accident
Jukka K. Korpela wrote:
> Harlan Messinger <hmessinger.removethis@comcast.net> scripsit:
>
> > If your goal is to provide users with a way to clear their entries and
> > start over, relying on them to guess that refreshing the page might
> > work isn't the way to go about it anyway.
>
> That's correct!
>
> > That's what the Reset button is for:
> > <input type="reset" name="reset" value="Reset">
>
> No! The "reset" button - which should be called destruction button - is for
> causing serious frustration when the user hits it by accident. It has other
> destructive features too.
>
> Well, maybe it _was_ for the purpose you describe, but it was spoiled by
> making it an almost "standard" button that "has" to reside alongside with
> the submit button, just to give users a sporting chance of wiping out all of
> their input irrecoverably.
>
> The constructive method is that the form handler, after checking and
> processing the form data and doing something with it, echoes back a result
> page. That page should tell whatever the user needs to know about the
> processing. Moreover, if deemed useful, it may then contain a fresh form for
> entering a new set of data.
>
> --
> Jukka K. Korpela ("Yucca")
> http://www.cs.tut.fi/~jkorpela/
Navigation:
[Reply to this message]
|