173565 - Satchel should replace password manager

Status: VERIFIED FIXED

(Toolkit :: Password Manager, enhancement)

Description

[Blake Ross]

Comment 1

[Neil Cronin]

*** Bug 176314 has been marked as a duplicate of this bug. ***

Comment 2

[David P James]

*** Bug 177156 has been marked as a duplicate of this bug. ***

Comment 3

[Jonas Jørgensen]

*** Bug 176155 has been marked as a duplicate of this bug. ***

Comment 4

[Sébastien Delahaye]

*** Bug 180509 has been marked as a duplicate of this bug. ***

Comment 5

[Sébastien Delahaye]

*** Bug 181390 has been marked as a duplicate of this bug. ***

Comment 6

[Sébastien Delahaye]

*** Bug 182848 has been marked as a duplicate of this bug. ***

Comment 7

[Sébastien Delahaye]

*** Bug 183099 has been marked as a duplicate of this bug. ***

Comment 8

[alanjstr]

I guess this is probably the place to put this:
In Phoenix 0.5 (and possibly earlier versions), in the JS Console, you can still
do Tools -> Password manager.  

Of course there is also a menu option for the JS Console on the JS Console.  

Comment 9

[André Dahlqvist]

*** Bug 183945 has been marked as a duplicate of this bug. ***

Comment 10

[Ben Goodger (use ben at mozilla dot org for email)]

One of the great things about password manager is that for situations in which
you only have one username/pass for a given site (i.e. most cases) the info is
just prefilled automatically when the page loads, meaning you don't need to
click-down-arrow-enter then grab the mouse again to click "Login". Logging in
becomes a single mouse action rather than a series of actions. 

That said, my belief is that the autocomplete system used by satchel is the best
way to show and select between multiple logins for a given page (rather than the
current dialog). 

Comment 11

[Pierre Chanial]

I concur with Ben, if there are several possibilities, I think that the focus
should be on the identity form, the autocomplete widget open. Selecting an
identity should prefill the password on the fly.

However, there would be a benefit only in the edge case of two or more identities
-> untargetting

Comment 12

[Blake Ross]

-> bryner

Comment 13

[David P James]

Taking QA. Sorry for the bugspam

Comment 14

[Steffen Wilberg]

We already have the new password manager. With one identity, it prefills forms;
with two or more, it uses autocomplete.
-> fixed? Or does this bug ask for something else?

Comment 15

[David P James]

Adding [pwd-mngr] to summary of Password Manager bugs to facilitate querying.
Sorry for the bugspam.

Comment 16

[Jeremy M. Dolan]

Is there a spec for this somewhere, that shows why all of these myriad bugs have
been duped to this one, which has a blank description, or is this simply an idea
in some developers head, with no timeframe for implementation?

Comment 17

[Brian Ryner (not reading)]

I'm not sure what Blake meant by this either, but we've replaced wallet with a
new satchel-based password manager, so I'd consider this done.  Please file
separate bugs for any remaining issues.

Comment 18

[Steffen Wilberg]

That was done before 0.7 already -> setting target milestone to that.

Comment 19

[Jacek Piskozub]

Target Milestone and Priority should be changed by the bug owner only.

Comment 20

[David P James]

Well the fact is that satchel *DID* replace password manager as of FB0.7, so
it's no longer a "target" but a "fait accompli".

Verified fixed.

Comment 21

[Peter Lairo]

Sorry, this _may_ be unrelated: The case where the user might not remember the
first letter of the UN is *not discoverable*. I didn't know about
"down-arrow-to-reveal-all-UN/PW's" until I read this bug (no "normal" user will
find/read this bug). 

It may be better to bring up a dialog whenever a site is visited that requires
UN/PW _and_ FB has _several_ UN/PW's for that site.