Closed Bug 454803 Opened 16 years ago Closed 16 years ago

Password Manager opens once for every tab at startup

Categories

(Firefox :: Security, defect)

x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 356097

People

(Reporter: scout, Unassigned)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1b1pre) Gecko/20080910020329 Minefield/3.1b1pre
Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1b1pre) Gecko/20080910020329 Minefield/3.1b1pre

If I start up Firefox with several tabs which require a login, the Password Manager pops up N-fold and I must enter my master password for every site that asks for a password.

So, for instance, if I start up with three sites which require a login, the Password Manager dialog opens in three instances. I must enter my master password in each of them.

This worked better in Firefox 2: No matter how many sites with logins it started up with, I only had to enter the master password once.

The new (and arguably braindead) behavior appeared in 3.0 and hasn't changed in 3.0.1 or 3.1b1pre (I'm running the nightly build, currently).

Reproducible: Always

Steps to Reproduce:
1. set your Home Page to a combination of sites that require login; e.g https://bugzilla.mozilla.org/enter_bug.cgi|http://mail.google.com
2. Configure Firefox to start with your Home Page
3. Restart Firtefox
Actual Results:  
Two instances of the Password Manager dialog open, one atop the other. You must enter your master password in both of them, otherwise your password isn't entered in one of the password fields.

Expected Results:  
IMHO, only one PM dialog should show. As soon as you've entered your master password, passwords should be entered wherever necessary.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
I agree that bug 356097 seems to be the same as this. It's only odd that 356097 (and its many duplicates) have been around at least since Firefox 1.5 and I only experienced it after the upgrade to 3.0. Never happened to me with 1.5 or 2.0. 

Any explanation for that?
You need to log in before you can comment on or make changes to this bug.