I fear that someone will be able to access my machine, and therefore access certain important sites if I had the Password Manager save those passwords. So the obvious answer is to not use the Password Manager for those sites. However, I'm lazy. For example, when I go do my online banking I don't want to have to dig out my bank card and re-type that 16 digit PIN every time I visit the site. I would like for the Password Manager to be able to remember the username of that site only, so that when I visit its already typed in for me, and all I have to add is my password and I'm in.

I think implementing this would get a lot more people actually using the password manager. Personally, I don't use it for the same reason the reporter mentioned. Almost everyone I know refuses to store passwords in browsers also because of this. Although I agree that it's not a top priority bug, I do think that this is a high impact bug: meaning whenever this gets done it will be a very cool feature that will get its fair share of fanfare by a lot of people... This might get done sooner than _most_ future bugs I hope?

Reporter: Another solution to being wary of people acessing your computer is to encrypt all the password data. Password Manager already offsers this option, btw.

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

An alternative is to fix bug 79527. Fixing that bug would allow users to store just the username and not the password, but by using the form manager instead of the password manager. In addition, it would allow usernames to be stored even on pages where the password manager doesn't work. It would also allow usernames to be stored even if they are part of a larger form (currently, a field marked "user name" is saved as the user's full name, not a username).

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

Reassigning to new module owner.

As a workaround you can store login/password and manually delete the password from your password file. This suggests that this feature is easy to implement, since it already works for filling in the information. So an additional checkbox could ask if also the password should be stored. pi

Asking for 1.8a. This would be a killer feature. It also addresses the FUD concerns in bug 145797. pi

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

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614

Yes, still valid. Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1pre) Gecko/20090610 SeaMonkey/2.0b1pre Alas, I cannot confirm bugs.

It is still an important feature. Even more with the new database which you cannot edit manually anymore. pi

We're now using toolkit login manager, if we want a fix, that needs to be made there, so moving this to the correct product/component.

Can this be made a dependency of bug 398776?

This works for me if you specify to "Never remember for this site". The username previously submitted is still saved in form history so this just works. The only case which doesn't work is if you have multiple usernames on a site and only want to save some of them but that's not what this bug is about.