The thing is, it doesn’t/shouldn’t. It should only appear if there is a password field on the page and even then only if you do not have a vault entry for the web page. When a vault entry exists, autofill should instead displayed, like this:
That is what happens for me. Is your experience different?
If you have a website that you absolutely do not want to be stored in your vault and for it not to show the autofill popup, you can add it to the “blocked domains” at the very bottom of the autofill settings page.
it’s better now with the extension settings configd differently than default.
Right, I meant any website with a password field. I guess I hoped BW could decipher between a register page and login page cuz I’d never want to gen a pass on a login page. Anyway, I would provide more info if I really was having a unuiqe issue here, but ticking that settings makes this work good enough for me now. Thanks for everyone’s responses!
All it needs is to save the auto generated login after registering on a site, saving manually is madness. (I know I am coming from a non-programmer perspective, I assume it’s easier said than done)
But it’s so close to working.
Why even auto generate a registration for me if the extension isn’t going to save it… seriously, why would BW create a non-human readable password for you and then be like … aight good luck with that… it gives me grey hairs every time.
I like the popup when mousing into a password field to automatically fill saved vault information, but I don’t want BitWarden to attempt to generate passwords for me, not least because its implementation is buggy (here you can see it interfering with PayPal’s 2FA prompt):
Folks have asked for this for years to no avail. Often people reply as is they can’t understand with it means to disable generated passwords while still filling in existing passwords. I also want to disable the fill generated password function. I don’t use generated passwords at all and never want to see any mention of them or accidentally use one.
@taphead I moved your post into an existing feature request on the same topic.
@ChuckBaggett The inline password generation feature was released less than 7 months ago (version 2024.11.0), so I don’t think people have been requesting the ability to disable it “for years”…
100% agree. There are a lot of suggestions in here about how to work around what should be a simple, straightforward solution: an option to disable suggesting generated passwords.
… as I still don’t know where “…move it to the Bitwarden menu” (part of the title of this feature request) exactly would end up in the browser extension - and considering the last posts and probably the common request of all posts -, I would suggest, to slightly adjust this feature request and make it (only) about an “Option to disable the inline autofill menu generator”. (@Matt5@grb )
PS: Well, it already can be disabled, when the inline autofill menu is disabled - so an option to independently only disabling the inline autofill menu generator seems to be needed.
Note: I now changed the title of this feature request from“Remove the “fill generated password” autofill option and move it to the Bitwarden menu”to“Option to separately disable the “inline autofill menu generator” (withouth disabling the inline autofill menu itself)”.
I further optimized the topic title; the current version is: “Make ‘Fill generated password’ function optional in the inline autofill suggestions menu”. The staff notice at the top of the thread provides all other necessary context.
I hate to unnecessarily bump a topic, but I think it’s important to mention that this has been tripping up my elderly parents. They keep generating new passwords when trying to log in instead of filling their existing passwords, then getting confused, resetting their passwords, and not updating them in BitWarden. I’ve tried to disable inline auto generated passwords for them but it doesn’t seem like there is an option. They mainly use the inline autofill menu so disabling the inline menu doesn’t seem to be an issue.
Seeing that this feature is relatively new seems to explain how my parents had no issue using BitWarden before, so it’s frustrating that it’s worked well for so long only for it to recently change.
If they were happy using the previous versions, why not simply disable the inline autofill menus altogether and go back to the way it was before? Just uncheck the box for “Show autofill suggestions on form fields” under Settings > Autofill.
Like I said, they only know how to use the inline autofill because it pops up without them needing to remember what to click, so disabling autofill suggestions entirely does not work as a solution. There really needs to be a way to disable the inline password generator without entirely turning off inline autofill suggestions.
It seems silly to me that the only option is all-or-nothing when it comes to inline autofill and inline password generation.
Based on your previous typo (“issue”/“option”), I assumed your parents had started using Bitwarden before 2024 (when the inline autofill menus were not available at all). Until there is progress on this feature request, perhaps you can explore other autofill options for your parents.
A simple one is to click the Bitwarden icon at the top of the browser (visible if the browser extension has been pinned), and then click the desired account to autofill its credentials (this may be easier to do if you enable the option “Click items in autofill suggestions to fill” under Settings > Appearance). Three other possibilities are (1) autofill on page load, (2) keyboard shortcut, or (3) context menu.
Yeah it’s unfortunate that first messages in discourse are often non-editable due to the edit window being expired by the time first messages are approved.
I have tried to teach my parents these alternative methods, but unfortunately due to their dementia nothing else really sticks - they really need something that proactively pops up for them to remember (and to prevent them from resetting their passwords weekly). I considered using auto-fill, but since they are the least tech-savvy people and also share a single “family laptop”, it gets confusing for them when they are trying to sign into a specific account - having the inline autofill automatically present them with available accounts has been the best option so far.
Currently one of my login workflows from a “locked” state when I want to fill a name+password on some website:
Click on the password field
Get a helpful popup from BW that it’s locked, so press a button to unlock it and enter BW password
Wait for BW to log in and get the unwanted popup with a suggestion to autofill a random/autogenerated password instead of desired popup with my website account name.
I guess this happens because it takes time for the vault to be fully loaded after logging in, so the default functionality for a website without a BW account kicks in and it offers you to fill in a random password first.
But I never use this function, I autogenerate passwords within the new account fields, so this is never useful to me, but very often just some noise obscuring the real popup with my account name
So I’d like to have an extra Autofill option: “Never suggest autogenerated passwords”. Then I’ll simply get nothing while the vault is being loaded and then only my account name autofill suggestion will pop up
If this is a correct diagnosis, then the appropriate fix would be to automatically delay the appearance of the “Fill generated password” pop-up until after the vault has been fully decrypted/loaded in memory. Perhaps a spinner could be displayed in the meantime.
