user_pref("signon.expireMasterPassword", true) makes new window fail




15 years ago
13 years ago


(Reporter: Klaus Kusche, Assigned: Mitchell Stoltz (not reading bugmail))



Firefox Tracking Flags

(Not tracked)





15 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030831
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030831

Split from bug 151443 on request of the bug owner:

After upgrading from 1.2 to 1.3, 1.4 or 1.5beta, the electronic banking
application I use failed: When logging on, a new window opened as before, but
instead of starting the Javascript application in the new window, the new window
remained blank, no content was loaded. Connection is over https.

After some investigation, I found out that the problam was caused by the line
user_pref("signon.expireMasterPassword", true); 
in my prefs.js file: After deleting this line or setting it to false, the
banking application worked fine (as it did in 1.2).

* How did this line come into my prefs.js (I have no idea!)?
* Why does it make loading the application fail?
* What does this option mean or control, and to which option in the prefs dialog
does it correspond?
* Shouldn't mozilla at least display some kind of error message?

Reproducible: Always

Steps to Reproduce:
1. Start your mozilla with the pref file entry given above (and with keep-alive
and pipelining off!).
2. Go to the URL above.
3. Log in with one of the demo accounts provided.
Actual Results:  
A new window comes up, but remains empty.

Expected Results:  
The banking application should start in the new window.
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.