Make "Fill generated password" function optional in the inline autofill suggestions menu

[Nail1684]

@Marcapus Welcome to the forum!

@Marcapus

“For all those, who don’t use the inline autofill menu at all: just deactivate the inline autofill menu in the browser extension (Settings → Autofill → turn off “Show autofill suggestions on form fields”) and the inline autofill menu generator will vanish.”

I can’t help but disagree to the mod notice because, as Jack23 said :

@Jack23

Disabling autofill suggestions all together is not and will never be the answer

Did you see the “For all those, who don’t use the inline autofill menu at all:" part to that exact notice? – I mainly added that for those who dislike the inline generator and who already considered not using the inline autofill menu altogether. Of course it’s not a solution for this feature request here.

@Marcapus

I never used the inline password generator because I use Passphrases and the inline generator does not support them.

It does. In theory, the inline autofill generator uses the current settings of the main generator of the extension. But there still is this bug, which leads to changes in the main generator settings not affecting the inline autofill generator:

Current bug: Context menu & inline autofill menu password generation ignore parameters

Hi there First of all, the issue : When generating a new password using the context menu or the option that sometimes pop under a password field, the generated password uses the default parameters (password, 14 chars, etc.). I’ve been to the Bitwarden extension, clicked the Generator menu at the bottom, and changed the option for "passphrase, 4 word, cap words and addnumber). Even with those parameters, the generated passwords from the context menu are still using the default p…

[ajones]

I want to chime in and express my interest in this feature - that is, being able to disable the auto-filling of newly generated passwords, without disabling autofill suggestions as a whole. I made a longer post in another thread that details my flow and where auto-filling of generated passwords causes friction here: Generator history should omit/hide generated passwords that were never used (copied, saved, etc.) - #39 by ajones

As an aside, it took quite a bit more interaction with this forum than I had expected to be able to vote on this feature request (many minutes of browsing and posting that post)… it’s a bit of a bummer that those votes are given weight when someone having the described problem can’t vote on it unless they participate in the forum for some unspecified amount of time. I suspect many people that are significantly affected by problems that find these forums through internet searches simply leave without voting.

[storkinsj]

I am only here trying bitwarden because I literally could not believe 1password does this as LastPass did not. Suggesting to generate a password for a site that already has a password is really bad. Also to sign up for this forum, I allowed bitwarden to suggest a generated password. Which it promptly did not save. LastPass would immediately offer to save the new login.

Autofill is the main purpose of a password manager in the browser. If you are literally telling me I have to disable autofill to stop your software from erroneously suggesting an unguessable password without guessing I would like you to save it is beyond debatably foolish.

[AlexCaswen]

The Generator Function as is in Bitwarden is an exercise in frustration, patience, and probably the worst part about the app.

I HATE IT. I HATE IT. I HATE IT.

This just happened to me: I am making a new Bitwarden Account, for business purposes. Starting with free, but if I am successful will totally be tempted to upgrade to paid. So I make a new account, and manually make the entry using the Chrome Extension, and save it, then copy and paste the generated password into the password entry field, and click “Create Account.”

But Inline Password Generator has a different idea, it replaces my copy and pasted password with it’s own, and then automatically updates the login details. Later, when I go to login to the Vault of the new Bitwarden project account, I can’t because the password that I saved to my personal account isn’t the one that the inline automatic generator replaced it with.

So frustrating.

So I solve this by painstakeningly going one - buy - one back through the generated password history, and eventually one of them works and I managed to login to the new account, and I use that to update the login details in my personal account.

• User UI FLOW: For a good user experience, the user of the app should feel in control of the app.
• The App should not do anything without direct user request for that action to happen.
• Password Generator does’t match this experience.
• When the user opens Password Generator, a password SHOULD NOT automatically be generated.
• When the user is signing up, Password Generator SHOULD NOT automatically suggest a password.
• Alternatively, the inline feature should be able to be granularly disabled.
• Alternatively, website metadata: (Url, date, time) should be appended to Generated Password History.
• Generated Password History should have expiry dates. Right now it lasts forever, this isn’t secure.

Sorry if this rant is a bit much but the Password Generator is BY FAR the most annoying and dysfunctional feature of what is otherwise an amazing app experience.