BW autofill vs Chrome autofill

Would like to see a feature in Bitwarden that recognizes chrome/edge/etc, autofill fields that those browsers may have stored. Many times the autofill suggestions for a browser overlays the bitwarden autofill, which I think is important too. I don’t want to turn off the browser autofill, it is helpful sometimes… maybe the autofill suggestions for bitwarden can be moved over more?

@marklyn Welcome to the forum!

Generally, the browser’s autofill functionality will interfere with Bitwarden’s browser extension, and vice versa, so it is not recommended to attempt to use both at the same time. The only exception would be if you use Bitwarden for only for autofilling login credentials, and do not use Bitwarden for autofilling of payment or contact information, then you could keep the browser functions for autofilling payment/contact information enabled (disabling only the browser’s password manager).

2 Likes

OK. I’ll have to work on BW to better recognize some sites, perhaps fine tune more. Hard to explain why sometimes both are used but I understand. Thanks

If there are specific sites you are having trouble with, let us know which one(s).

Thanks. I will.

1 Like

This is an example where Chrome wants to give a default suggestion for an email address I don’t really use for anything vs what I now can’t see for my united mileage login. I don’t want to completely turn off autofill for chrome because I do use it for some sites that Bitdefender has a difficult time recognizing (still trying to find those for you). I suppose I need to fix any and all sites that haven’t been working with bw or let you know those sites.

Yes. In the meantime, you should still be able to autofill the forms that are blocked by Chrome’s pop-up menu, either by using the keyboard shortcut (Ctrl+Shift+L on Windows), or by right-clicking the input field and selecting Bitwarden > Autofill Login > [account] in the context menu, or by opening the browser extension window and clicking Fill.

I’ve found that BW’s autofill just doesn’t give as smart autofill recommendations for certain text fields that it recognizes vs. Brave Browser (chrome).

I tried keeping just the address autofill, but I believe the browser would always still prompt me to save passwords as a result. Is there a way to stop that? If I recall, I couldn’t find an option to disable that constant prompt.

As an example of a page that BW doesn’t seem to recognize: Schedule a Pickup | USPS

Yes. In Chrome, you would go to chrome://password-manager/settings and disable the option “Offer to save passwords and passkeys”. There is a similar setting in Brave.

 

I concede that the inline autofill pop-up menu (an option I personally prefer not to use) does not appear on this site. Nonetheless, the form can readily be autofilled using Bitwarden’s extension window, or the right-click context menu, or the keyboard shortcut option.

You can use this link to report the failure of the inline autofill menu for the USPS site:

Thanks for the google doc, I’ll submit a new site when I find it. If the extension can recognize where to autofill when you do it via the extension window, why can’t it do it inline, too? I’m sure there’s a technical reason I’m not considering.

I have the same problem as the previous user, where if I leave chrome’s (in my opinion, smarter inline autofill) enabled, it will often overlay with the BW inline autofill, which is a pain. The other ways of filling do work but take a few more seconds which is why I like the inline version. Gotta go fast!

As I explained to the other user, you can selectively disable inline autofill pop-ups by either Chrome or Bitwarden for passwords, addresses, and/or payment information. You will only have interference problems if both Chrome and Bitwarden are enabled to autofill a specific type of data (passwords, addresses, or payment information), so for each data type, you need to choose which service you want to handle the autofilling.

Inline autofill looks for password fields when the page is first loaded. Websites that add the field later (even just a second) will miss out. Ctl-shift-L autofill looks for the field at the time you type the shortcut, so there is a much better chance of the field existing.