Closed Bug 268196 Opened 20 years ago Closed 20 years ago

Clicking cancel on password prompt opens new prompt when viewing saved passwords

Categories

(Toolkit :: Password Manager, defect)

x86
Windows 98
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 237610

People

(Reporter: jason, Assigned: bryner)

Details

User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.5) Gecko/20041103 Firefox/1.0RC2 Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.5) Gecko/20041103 Firefox/1.0RC2 If I start firefox, and go Tools > Options, Privacy, then expand Saved Passwords, and click the "View Passwords" button, I am given a prompt for my master password. Clicking cancel on this prompt does seem to close the prompt, but a new prompt is open. By my testing, it appears that the number of prompts given is the same as the number of passwords stored. Once you've finally hit cancel for the last time, the password manager dialog is given (despite the fact I hit cancel!), but with no passwords listed (even if I have some stored.) Reproducible: Always Steps to Reproduce: 1. Save several (at least two) passwords, and set a master password. 2. Close and reopen firefox. 3. Go to the privacy options, expand saved passwords, and click View Saved Passwords. 4. Click cancel. Actual Results: Prompt reappears for password. After continually clicking cancel, the manager UI is given, but without any passwords listed. Expected Results: Cancel the prompt, and not open the manager UI. Tested with the default theme, using RC2 obtained via the updater. Seems simliar to bug 237610, which is filed for the mozilla suite. Also confirmed with new profile.
Its a bug in PSM, which is shared between all Gecko apps. Duping. *** This bug has been marked as a duplicate of 237610 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Ah. Didn't know that the password manager was shared code. Bug 237610 and this bug probably have the same root cause. Sorry for the dupe.
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.