Closed Bug 251959 Opened 20 years ago Closed 20 years ago

Password manager firefox meta bug

Categories

(Toolkit :: Password Manager, defect)

x86
Linux
defect
Not set
major

Tracking

()

RESOLVED INVALID

People

(Reporter: davidgrant, Assigned: bryner)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040704 Firefox/0.9.1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040704 Firefox/0.9.1

I'm getting confused by all the multiple reports of password manager bugs.  I
think it would be a good idea to group the main ones here and perhaps a lot of
the other ones would actually just be dupes.

Reproducible: Always
Steps to Reproduce:
Depends on: 249940, 250111
Summary: Password manager meta bug → Password manager firefox meta bug
Depends on: 236683, 247677, 249329
Summary: Password manager firefox meta bug → [meta] Password manager critical firefox bugs
Depends on: 221634
Depends on: 218694
No longer depends on: 221634, 236683, 247677, 249329, 249940, 250111
Depends on: 221634, 236683, 247677, 249329, 249940, 250111
No longer depends on: 218694
Summary: [meta] Password manager critical firefox bugs → Password manager meta bug
Sorry for all the messages which must have been sent out while I started this
bug.  I feel it is necessary to create such a bug because I feel that the
password manager is fairly broken in Firefox yet it worked fine in Mozilla.
Summary: Password manager meta bug → Password manager firefox meta bug
Depends on: 218694
Creating a meta bug this generic is pointless and just causes more spam.  This
is why we have components like "Password Manager" in Bugzilla, to keep things
separate by component.  Meta bugs are only useful when tracking specific subsets
of bugs.  This just seems to be a random collection of password manager bugs, 3
of 7 being unconfirmed.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
No longer depends on: 218694, 221634, 236683, 247677, 249329, 249940, 250111
Resolution: --- → INVALID
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.