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)”.
