Edit>Undo should undo form resets[form sub]

NEW
Unassigned

Status

()

Core
HTML: Form Submission
P4
enhancement
17 years ago
9 years ago

People

(Reporter: timeless, Unassigned)

Tracking

({dataloss})

Trunk
mozilla1.1alpha
dataloss
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

17 years ago
I just accidentally clicked the Reset button on a bugzilla form and all my work
was lost.  If I could have gone to edit>undo i would have been very happy.

Comment 1

17 years ago
This won't happen until after we move Reset from frames to content.  Adding
dependency.  BTW, we'll keep this in mind when we move values over and design
the values such that they *can* be stored and restored.
Depends on: 34297

Updated

17 years ago
Keywords: dataloss
Summary: Please make Edit>Undo undo Form Resets → Edit>Undo should undo form resets

Comment 2

17 years ago
reassinging to new owner of form submission
Assignee: rods → alexsavulov

Updated

17 years ago
Summary: Edit>Undo should undo form resets → Edit>Undo should undo form resets[form sub]

Comment 3

17 years ago
I'd agree wholeheartedly with this idea, if it weren't for the fact it would be
a security problem. For example ... There's a kiosk at the University of
Canterbury Library, running Mozilla 4.x, open on a Web page which lets you
transfer money from your computer services account to your library account and
vice versa. The idea is that when you've finished, you click the `Reset' button
so that no-one can mess around with your account, or use fancy bookmarklets to
read your password from the form field, or whatever. If a reset could be Undone,
it would blow a big hole in this process.
*** Bug 117691 has been marked as a duplicate of this bug. ***
OS: FreeBSD → All
Hardware: PC → All

Comment 5

17 years ago
this would be a very wellcome enhancement i suppose

setting milestone
Target Milestone: --- → mozilla1.1

Comment 6

17 years ago
Storing all that info in the undo list would get expensive, wouldn't it?  At any
rate, whoever implements this finally should keep in mind that this should only
happen when the user hits the Reset button, not every time JS calls .reset() or
we call reset internally ... and we do that frequently on individual controls.

This should just be a matter of storing a hash from content pointers to values
(probably nsISupports or something).  For select it gets somewhat tricky, but it
could be as simple as storing an array or a comma-separated list of indices
(probably a comma-separated string will be more space-efficient, which is really
the trick here).

Updated

17 years ago
Priority: -- → P4

Comment 7

15 years ago
My solution is a user style sheet rule:

input[type="reset"], button[type="reset"] { display:none }

Comment 8

15 years ago
mpt: passwords should be omitted from the undo-reset data.  That would be
similar to the solution to bug 65947, "form password is remembered when hitting
back button" (fixed).

Comment 9

15 years ago
*** Bug 239668 has been marked as a duplicate of this bug. ***
Assignee: alexsavulov → nobody
QA Contact: vladimire → form-submission
You need to log in before you can comment on or make changes to this bug.