Open Bug 1387302 Opened 5 years ago Updated 3 years ago

When importing multiple usernames/passwords for the same domain from Chrome it is hard to remember which is the default

Categories

(Firefox :: Migration, enhancement, P3)

enhancement

Tracking

()

People

(Reporter: pdol, Unassigned)

Details

We've noticed in user testing videos, when a user imports data from another browser (Chrome in this case), if there are multiple usernames/passwords for the same domain, users forget which their default one is, causing them to not be able to login to that website until they figure out which is the right one to use.  
This is because they've been using a default on Chrome even if they have more than one username/password, so they don't need to remember.

This is a poor first experience in Firefox as it looks as though Firefox didn't properly import the right password when they choose the wrong one.

If there is a way to determine which username/password is the one commonly used in Chrome for that domain, we should default to it in password manager so the user doesn't need to guess.

Ping me if you want an example video.  It has personal information in it.
Chrome has the concept of a default login? Is it for the site or page or what? We don't have such a concept: if you have one saved login we autofill, otherwise you get a dropdown.

Did the user have two different accounts on this site? Or one? Were there two different saved usernames?
Priority: -- → P3

(In reply to Matthew N. [:MattN] (PM me if request are blocking you) from comment #1)

Chrome has the concept of a default login? Is it for the site or page or
what? We don't have such a concept: if you have one saved login we autofill,
otherwise you get a dropdown.

Did the user have two different accounts on this site? Or one? Were there
two different saved usernames?

Chrome autofills latest used (edited?) u/p for the selected domain. In the case of importing multiple u/p for the same domain (and now subdomains), Firefox ends up with multiple u/p, in which case, we don't autofill, we show autocomplete. The autocomplete is also ordered alphabetically and not by the last updated ("from this website").

You need to log in before you can comment on or make changes to this bug.