Closed
Bug 171756
Opened 23 years ago
Closed 16 years ago
add Confirmation dialog for Remove All passwords
Categories
(SeaMonkey :: Passwords & Permissions, defect)
SeaMonkey
Passwords & Permissions
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 390025
People
(Reporter: parish, Unassigned)
References
Details
(Keywords: dataloss)
Attachments
(1 file, 1 obsolete file)
|
21.99 KB,
patch
|
Details | Diff | Splinter Review |
On clicking the Remove All button in Password Manager a confirmation dialogue
should pop-up to help prevent accidentally deleting all saved passwords (I've
just discovered the hard way that this doesn't happen :-( )
Comment 1•23 years ago
|
||
[RFE] is deprecated in favor of severity: enhancement. They have the same meaning.
Severity: normal → enhancement
Comment 2•23 years ago
|
||
seems to me to be a legitimate RFE... confirming.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: [RFE] Confirmation dialogue required for Remove All → add Confirmation dialog for Remove All passwords
Reassigning to new owner.
Assignee: morse → dveditz
Comment 4•23 years ago
|
||
Please provide this. It caught me out yesterday, when I clicked on the wrong
button. Either a confirmation, or a select All and then remove, as that is at
least two steps.
That is a better idea; get rid of the Remove All button and force the user to
select all (Shift-click or Ctrl-A, on Windows) and then click Remove.
Is there any good reason for having a Remove All button?
This solution will also have the added benefit of /reducing/ the Mozilla code
rather than adding even more.
If there are no objections to this idea then I'll whip up a patch.
Patch that gets rid of the Remove All buttons on all the Manager windows (for
UI consistency).
popupManager.js:clearTree() is now obsolete.
Attachment #115980 -
Attachment is obsolete: true
*** Bug 207371 has been marked as a duplicate of this bug. ***
Comment 9•23 years ago
|
||
*** Bug 208790 has been marked as a duplicate of this bug. ***
Comment 10•22 years ago
|
||
*** Bug 215410 has been marked as a duplicate of this bug. ***
Comment 11•22 years ago
|
||
*** Bug 234731 has been marked as a duplicate of this bug. ***
Comment 12•21 years ago
|
||
Even with the confirm dialog, there should be an undo command in case of rushed
accidents. I just lost some passwords too. ;_;
Updated•21 years ago
|
Product: Browser → Seamonkey
Comment 13•21 years ago
|
||
And I just lost passwords. Why hasn't this been rolled out yet, after 2.5
years? What needs to happen to get this problem fixed?
I'd hoped that clicking on 'cancel' in the parent window, the main Preferences
dialogue, would cancel my oops. No such luck.
Comment 14•21 years ago
|
||
Comment on attachment 115981 [details] [diff] [review]
Remove clearTree()
This stuff looks good but as IanN moved everything around recently someone will
need to fix this up before requesting review from mvl or dwitte or whomever.
Keywords: dataloss,
helpwanted
Comment 15•20 years ago
|
||
Why isn't the status of this changed to verified?
I lost my passwords like this too. Please include this feature as soon as possible.
I don't think including an undo feature (as someone else requested) is a must,
but it would certainly be an added plus. But undo should not be possible after
one has hit "OK" in the password manager window.
And Select All > Remove seems a good idea, as is making it the same for all the
Manager (I assume Cookie Manager too) windows. Though I have used Remove All in
the cookie manager window often, I can sacrifice that to get some other
advantage - namely of avoiding accidental erasure.
Comment 16•20 years ago
|
||
I request change of priority to normal, since losing vital information such as
passwords is hardly an "enhancement" issue. Hopefully this change will also
prompt someone to come up with a fix for this bug which lies unattended for
about at least two and a half years. Please guys, help us simple end-users who
don't know to create a fix ourselves. Thanks!
Comment 17•20 years ago
|
||
This should not be in a release version. Requesting a block on final.
Flags: blocking-seamonkey1.0?
It's too late now, and there isn't any (recent) patch. You can nominate this for SM1.1 in bug 315312 if you'd like.
Flags: blocking-seamonkey1.0? → blocking-seamonkey1.0-
Comment 19•20 years ago
|
||
(In reply to comment #18)
> It's too late now, and there isn't any (recent) patch. You can nominate this
> for SM1.1 in bug 315312 if you'd like.
>
"You tried to change the Blocks field , but only the assignee or reporter of the bug, or a sufficiently empowered user may change that field."
Updated•20 years ago
|
Assignee: dveditz → nobody
Updated•18 years ago
|
QA Contact: tpreston
Comment 20•16 years ago
|
||
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.3a1pre) Gecko/20090913 Shredder/3.1a1pre
Current Thunderbird 3 nightly has the behaviour requested by this bug.
Maybe SeaMonkey happens to share the same code?
Do you still see this bug in current SeaMonkey nightlies? (Please mention your version)
Severity: enhancement → normal
Comment 21•16 years ago
|
||
This has been fixed in SM 2 (through the switch to satchel and the new Password Manager dialog, bug 390025).
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
Comment 22•16 years ago
|
||
V.Duplicate
You need to log in
before you can comment on or make changes to this bug.
Description
•