Closed
Bug 327005
Opened 20 years ago
Closed 13 years ago
password manager prefs not set
Categories
(Toolkit Graveyard :: XULRunner, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: chpe, Unassigned)
Details
XULrunner includes passwordmanager, but the prefs that enable it aren't set.
Those prefs are set to this in ff:
http://lxr.mozilla.org/seamonkey/source/browser/app/profile/firefox.js#362 :
362 pref("signon.rememberSignons", true);
363 pref("signon.expireMasterPassword", false);
364 pref("signon.SignonFileName", "signons.txt");
Even if you don't want to turn it on by default, IMHO these prefs should be included (with rememberSignons=true in that case), so embedders just have to flip one pref instead of adding any number of undocumented prefs.
So what happens without these prefs? Do you get JS or some other kind of errors? Or you're just never offered the opportunity to remember passwords?
Reporter | ||
Comment 2•19 years ago
|
||
When the pref isn't set, you don't get password prefill in web forms, and no prompt to save the password data on submit.
Comment 3•19 years ago
|
||
I'm now getting an ASSERT when I start up XULRunner
ASSERTION: Fallback for signon filename not present: '!signonFile.IsEmpty()', file d:/Mozilla/mozilla/toolkit/components/passwordmgr/base/nsPasswordManager.cpp, line 1733
This didn't happen last week.
Reporter | ||
Comment 4•19 years ago
|
||
(In reply to comment #3)
> I'm now getting an ASSERT when I start up XULRunner
>
> ASSERTION: Fallback for signon filename not present: '!signonFile.IsEmpty()',
> file
> d:/Mozilla/mozilla/toolkit/components/passwordmgr/base/nsPasswordManager.cpp,
> line 1733
>
> This didn't happen last week.
I think that a problem's from the patch from bug 221634.
Comment 5•13 years ago
|
||
I'm not going to track this. If somebody wants to fix this, they may reopen it and provide a patch.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → INCOMPLETE
Assignee | ||
Updated•10 years ago
|
Product: Toolkit → Toolkit Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•