Talk:Toolkit:Password Manager

Why should it matter whether Firefox is the default browser? IMHO, the keychain should be used for the UN/PW store regardless of the default browser. What's the down side to having a UN/PW store common to several browsers?

Integration of stored passwords

Wouldn't it be nice to integrate the stored passwords much more in the browser to the bookmarks for a faster browser experience? I think a lot of pages with passwords are just to log in - they have no more use. And this log in could be completely automated with an option for doing so on the bookmark for the page. E.g. a bookmark for page http(s)://login.xyz.com should have something like a drop down menu with the option to

i) Open the bookmark itself (by simply clicking on it)

ii) Directly log in to it (by clicking on the login name in the dropdown menu)

that kind of login could be very fast because the browser don't need to load the hole page and it even don't need to render it fully. By clicking on "ii)" the user would be directly forwarded to the secure area after the login. It's just an idea, but I think it would be very useful, simple to use, and fast!

Manage passwords per page?

Instead of the domain name, the full path should be stored. E.g. for a website "http://www.phpbb.com/forum/index.php?c=3", the stored location should be "www.phpbb.com/forum/index.php" instead of just "www.phpbb.com".

Why?

Example: A forum like phpBB uses the same field names for different purposes. If you want to edit other users in the administration panel, currently Firefox will overwrite the user name and password with the login info of the admin. Very annoying.

Admittedly in this case it could be resolved by the developers of the forum, but I think there are situations where you don't want or can force different name fields for each website hosted on the same domain. --Pizzahut 12:51, 27 March 2006 (PST)