How can I store passwords that have been deleted
I had usernames and passwords stored for several e-mail accounts on the same site. These were accidentally removed from the saved passwords list, and now I cannot get Firefox (23.0) to remember them again. I do have password saving enabled (behind a master password), and this site does not appear on the 'exceptions list.' In the Manage Password utility, there is no facility to add new passwords, only remove them. It seems, once removed, Firefox assumes one will never want to save this site again.
I'm in and out of these accounts literally dozens of times per day, and now have to log in manual every single time. How can I get Firefox to save these username/password combinations for me again?
Solution eye eponami
Yes. autocomplete=off is a direction that web sites can give to a browser to instruct them not to store the data that you enter in an input field. That can be search terms that you enter on a website like Google, but also privacy or security sensitive data like a credit card number.
If you use the bookmarklet then you are aware what you are doing and give it a second thought.
If you use the extension then you won't notice that a website prefers that you do not to save this data.
With saving a password you need to confirm a prompt, but other form data may get remembered unnoticeable if autocomplete=off is removed.
Tanga eyano oyo ndenge esengeli 👍 1All Replies (10)
hello, websites can define that the browser shouldn't save passwords in their source-code, see Usernames and passwords are not saved
you could use an addon like the following to circumvent such restrictions: https://addons.mozilla.org/firefox/addon/remember-passwords
I appreciate the quick reply, but please *read* what I posted. This is *not* a website security issue; I've had the passwords on this website stored for years. It's that once I accidentally removed them from my list, Firefox won't allow me to add them back in. I want to be able to get Firefox's *built-in password manager* to simply REsave my passwords, hopefully without removing and reinstalling Firefox. I don't want yet another third-party add-on; I already use so many that my browser is a sluggish mess and friend yell at me for 'too many add-ons' (currently 22 active). Let me try to restate my question in *simpler* terms:
How can I make Firefox pw manager RE-save a lost username/password (that was working fine before I deleted it)???
many major sites (google, yahoo) have changed the attribute on their site that passwords shouldn't be stored quite recently - so this wouldn't have affected you if you've used the sites for years and the password has already been saved.
Ah, thanks, that fully explains it then. Very sorry I accidentally removed them. Guess I'm going to have 23 add-ons now. Thanks for the tip on that add-on.
You can also remove autocomplete=off with a bookmarklet to make Firefox save names and passwords and other form data.
Thanks, @Cor-el. I'd actually found that article before posting, but was too stupid to fully understand it. After re-reading it, I *think* get it, but wonder if the 'autocomplete=off' means it won't autocomplete when I double-click in the 'username' field on the form?
Before I accidentally removed the stored passwords for the site (Yahoo mail), all I had to do was doubleclick on the username field, choose which username, and the pw was then filled in automatically. That's what I'm trying to get back to. I just installed the add-on and it's working just fine.
Would I get the same result by doing the bookmarklet, but removing the add-on (or could I remove the add-on now that I have the ones restored that I was after)?
The only reason I want to remove the add-on is because my geekier friends keep telling me I have "too many add-ons" and that it make my browser painfully slow.
Solution eye oponami
Yes. autocomplete=off is a direction that web sites can give to a browser to instruct them not to store the data that you enter in an input field. That can be search terms that you enter on a website like Google, but also privacy or security sensitive data like a credit card number.
If you use the bookmarklet then you are aware what you are doing and give it a second thought.
If you use the extension then you won't notice that a website prefers that you do not to save this data.
With saving a password you need to confirm a prompt, but other form data may get remembered unnoticeable if autocomplete=off is removed.
Ezalaki modifié
now that you have saved the passwords again, you can remove the addon. it (or the bookmarklet) is not necessary for subsequent visits if the password is already stored in the password manager.
@Cor-el Thanks *so* much! That clears it up mostly. I think you're saying both do essentially the same thing, but the extension becomes totally transparent to the user where as the bookmarklet approach requires an affirmative action by the user for each website. Since the extension is doing what I want, easily, and has restored the user/pw combos I was concerned about, I'll just leave it (or can disable it now until needed again). I promise not to use it on my online banking sites! :)
@philipp Thank you too! Between the two of you, I've fixed this annoyance. I'll hack through some of the others here later. Much appreciated!
I have my saved username/password pairs back in saved passwords, so I'm happy, and this next point is really nitpicky now, but sometime recently, after Yahoo forced users out of Classic Mail (I'd found a workaround and held onto Classic until a month or two ago, when they plugged that hole), and probably the same time they made the change @phillip mentioned, when I log out of one account and into another, the login page comes up but the saved form history (and subsequent password) won't show up on the first try - I have to reload the page, then clicking in that field brings up the username choices.
I'm wondering if using the 'bookmarklet' method would fix this minor issue, or if it's just a case of me clicking there before the (slow, Flash-based POS that is the new Yahoo Mail) page finishes loading and interrupts a script or something. Again, I don' t really know how *any* of this stuff actually works, just taking stabs in the dark at possible causes. Anyone know what might be doing this?