Closed
Bug 121443
Opened 23 years ago
Closed 19 years ago
Default Button for Save Password Dialog should be "No"
Categories
(SeaMonkey :: Passwords & Permissions, defect)
SeaMonkey
Passwords & Permissions
Tracking
(Not tracked)
RESOLVED
FIXED
Future
People
(Reporter: leealwc, Assigned: ajschult784)
References
Details
Attachments
(1 file)
1.11 KB,
patch
|
neil
:
review+
neil
:
superreview+
asa
:
approval1.8b3+
|
Details | Diff | Splinter Review |
I think the default button for the Save Password dialog should be "No", so that people don't save the password by accident by pressing "Enter".
Updated•22 years ago
|
Status: NEW → ASSIGNED
Target Milestone: --- → Future
Comment 2•22 years ago
|
||
*** Bug 184318 has been marked as a duplicate of this bug. ***
Reassigning to new module owner.
Assignee: morse → dveditz
Status: ASSIGNED → NEW
Comment 4•21 years ago
|
||
Depends on redesign of this dialog. Reporter, do you have a use case of a situation where accidentally saving the password is a bigger disadvantage than accidentally NOT saving it?
Depends on: 101338
Comment 5•21 years ago
|
||
well, this was mostly a firebird problem for me, back when it didn't have a way to disable password saving. i'd fill in my username and password, hit return, hit return again by instinct, and end up with the password saved even when i didn't mean to. this was especially bad because there was (at the time) no way to clear saved passwords. in any case, i feel that saving sensitive data to disk by default is non-ideal, especially since passwords are only obscured by default. also, when many users share a machine, a unintentionally saved password could mean that an unauthorized user can gain access to something he shouldn't. better the default be the safer option, i feel.
Agree with Jonathan. Defaulting to "Yes" might be more convenient, but considering the potential consequence of accidentally saving/not-saving the password, I'd prefer the safer option. accidentally saving password: - could leak sensitive password, especially with multi-user machines accidentally not saving password: - type again next time... :)
Comment 7•21 years ago
|
||
Most definately agree. That is first question asked by users using Mozilla in a non trusted environments (multiple users sharing profile, libraries, internet cafes etc) why passwords by default are saved. Users tend to hit Enter on dialog windows without reading them.. and saving one's password should be conscious decision.
Comment 8•21 years ago
|
||
Disagree. It acts this way now, and I hate it myself.
Comment 9•20 years ago
|
||
*** Bug 240975 has been marked as a duplicate of this bug. ***
Comment 10•20 years ago
|
||
Bug 263532 is the same bug for Firefox.
Updated•20 years ago
|
Product: Browser → Seamonkey
Updated•19 years ago
|
Flags: blocking-seamonkey1.0a?
Not blocking for this bug, but I would like to see it fixed.
Flags: blocking-seamonkey1.0a? → blocking-seamonkey1.0a-
Assignee | ||
Comment 12•19 years ago
|
||
Assignee: dveditz → ajschult
Status: NEW → ASSIGNED
Attachment #186695 -
Flags: superreview?(neil.parkwaycc.co.uk)
Attachment #186695 -
Flags: review?(neil.parkwaycc.co.uk)
Comment 13•19 years ago
|
||
note that this patch also affects the "save form info" dialog (which I think is a good thing)
Comment 14•19 years ago
|
||
Comment on attachment 186695 [details] [diff] [review] patch Although I couldn't persuade the form fill dialog to popup, the password manager correctly defaults to no.
Attachment #186695 -
Flags: superreview?(neil.parkwaycc.co.uk)
Attachment #186695 -
Flags: superreview+
Attachment #186695 -
Flags: review?(neil.parkwaycc.co.uk)
Attachment #186695 -
Flags: review+
Assignee | ||
Comment 15•19 years ago
|
||
Comment on attachment 186695 [details] [diff] [review] patch low risk change to make "no" default for password-saving and form data-saving.
Attachment #186695 -
Flags: approval1.8b3?
Updated•19 years ago
|
Attachment #186695 -
Flags: approval1.8b3? → approval1.8b3+
Comment 16•19 years ago
|
||
checked in.
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Comment 17•19 years ago
|
||
Now is better, thanks. What about bug 263532? It's other product but it's the same problem.
You need to log in
before you can comment on or make changes to this bug.
Description
•