This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 4480 - "reset this form" is not a good option
Summary: "reset this form" is not a good option
Alias: None
Product: Validator
Classification: Unclassified
Component: Website (show other bugs)
Version: 0.8.0b1
Hardware: All Linux
: P2 normal
Target Milestone: 0.8.0
Assignee: Olivier Thereaux
QA Contact: qa-dev tracking
Depends on:
Reported: 2007-04-20 09:38 UTC by PatomaS
Modified: 2007-04-24 01:37 UTC (History)
0 users

See Also:


Description PatomaS 2007-04-20 09:38:28 UTC

The button "reset this form" is a usability problem.

There is no good reason to reset the options of the form once you have changed it.  And that button can make a big mess with corrections made to erroneus code.

Imagine this situation:
1. I paste the code in the textarea for that purpose and press the "validate this document" button.
2. The validator detects some errors, lets say 3.
3. i go back with the brwoser back button and change 2 of the errors, i pres the validate button again and the system tells me that I still have one error, so I go back once again
4. I change the last error and press the reset button by mistake
5. uuuups
6. @#!!$##

Yes, it is my mistake, but it won't happen if the button is not there.

Plus there is another problem, but it could be in a second bug report and is that once i pres the validate button, if i press the reset button, the form gets reseted, but the browser still shows signs of waiting for information from the server, so it seems tha the reset button only works in the page, so it is even more unuseful. If the answer to the bug report is that there is a good reason for the button to stay, i will fill another bug with the second idea.


Bye, and keep up with the excelent work.
Comment 1 Olivier Thereaux 2007-04-24 01:37:47 UTC
Hi Patomas,

(In reply to comment #0)
> The button "reset this form" is a usability problem.

I have to say you challenged my preconceived ideas. First thought was "it would be bad to cripple the interface because human error happens" but after some reflection, and a lot of reading of opinion pieces on the usability of the reset button (or lack thereof) I'm not sure I have a clear case for having this button in the first place...

I also know the location of the reset button is an issue (insert mac/pc UI guidelines rant here) and I understand it can reall be a frustrating issue.

Over all I think I am convinced. (Anyone disagreeing can reopen this bug with a clear argumentation, thanks!)

I have removed the reset button from the version in CVS, which will be up at the next beta/release.

Thank you.