Open
Bug 100988
Opened 23 years ago
Updated 2 years ago
Edit>Undo should undo form resets[form sub]
Categories
(Core :: DOM: Core & HTML, enhancement, P4)
Core
DOM: Core & HTML
Tracking
()
NEW
mozilla1.1alpha
People
(Reporter: timeless, Unassigned)
References
Details
(Keywords: dataloss)
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•23 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•23 years ago
|
Keywords: dataloss
Summary: Please make Edit>Undo undo Form Resets → Edit>Undo should undo form resets
Updated•23 years ago
|
Summary: Edit>Undo should undo form resets → Edit>Undo should undo form resets[form sub]
Comment 3•23 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.
Comment 4•23 years ago
|
||
*** Bug 117691 has been marked as a duplicate of this bug. ***
Updated•23 years ago
|
OS: FreeBSD → All
Hardware: PC → All
Comment 5•23 years ago
|
||
this would be a very wellcome enhancement i suppose setting milestone
Target Milestone: --- → mozilla1.1
Comment 6•23 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•23 years ago
|
Priority: -- → P4
Comment 7•21 years ago
|
||
My solution is a user style sheet rule: input[type="reset"], button[type="reset"] { display:none }
Comment 8•21 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•20 years ago
|
||
*** Bug 239668 has been marked as a duplicate of this bug. ***
Updated•15 years ago
|
Assignee: alexsavulov → nobody
QA Contact: vladimire → form-submission
Assignee | ||
Updated•5 years ago
|
Component: HTML: Form Submission → DOM: Core & HTML
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•