Closed
Bug 443161
Opened 17 years ago
Closed 15 years ago
Remove incorrect |// Ignore 'autocomplete=off' - available only when wallet.crypto is enabled.|
Categories
(SeaMonkey :: Preferences, defect)
SeaMonkey
Preferences
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: sgautherie, Assigned: sgautherie)
References
Details
(Whiteboard: [Bug 390025 and bug 483458 eventually removed both preferences])
Attachments
(2 obsolete files)
(Noticed while looking into bug 425145.)
[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a5pre) Gecko/20070515 SeaMonkey/1.5a] (nightly) (W2Ksp4)
I am successfully using |wallet.crypto.autocompleteoverride = true|,
yet I have never set |wallet.crypto = true|.
Assignee | ||
Comment 1•17 years ago
|
||
Assignee | ||
Updated•17 years ago
|
Attachment #327801 -
Flags: review? → review?(iann_bugzilla)
Assignee | ||
Comment 2•17 years ago
|
||
Attachment #327802 -
Flags: review?(bugzilla)
Comment 3•17 years ago
|
||
Yes, its incorrect because someone broke it. The pref is meant to only work when a master password is protecting those passwords. The fact that it doesn't is a pretty crappy bug, IMO.
Assignee | ||
Comment 4•17 years ago
|
||
(In reply to comment #3)
Let's wait for bug 425145 then.
Depends on: 425145
Whiteboard: [Wait and see for bug 425145]
Comment 5•17 years ago
|
||
> Yes, its incorrect because someone broke it. The pref is meant to only work
> when a master password is protecting those passwords. The fact that it doesn't
> is a pretty crappy bug, IMO.
Hmm. As far as I can tell, this change was deliberate.
Comment 6•17 years ago
|
||
Comment on attachment 327802 [details] [diff] [review]
(Bv1-TB) <all-thunderbird.js>
Cancelling review request for the time being, as we're waiting for the outcome of different bugs.
Attachment #327802 -
Flags: review?(bugzilla)
Assignee | ||
Updated•17 years ago
|
Attachment #327801 -
Flags: review?(iann_bugzilla)
Comment 7•17 years ago
|
||
(In reply to comment #5)
> > Yes, its incorrect because someone broke it. The pref is meant to only work
> > when a master password is protecting those passwords. The fact that it doesn't
> > is a pretty crappy bug, IMO.
>
> Hmm. As far as I can tell, this change was deliberate.
Yes, and I think it was a bad decision. It was bug 154825 and I think it was rather poorly thought through.
Comment 8•15 years ago
|
||
This bug is open but targeted for seamonkey2.0a1, which has been released a long time ago. Please set the target milestone to an appropriate value, "---" if it has no specific target.
Assignee | ||
Updated•15 years ago
|
Target Milestone: seamonkey2.0a1 → ---
Assignee | ||
Updated•15 years ago
|
Assignee | ||
Updated•15 years ago
|
Attachment #327801 -
Attachment is obsolete: true
Assignee | ||
Updated•15 years ago
|
Attachment #327802 -
Attachment is obsolete: true
You need to log in
before you can comment on or make changes to this bug.
Description
•