When the web page contained an address or ID form, BW used to suggest IDs at the top of the list. But after a BW Firefox extension update (fairly recent, now on 2025.2.0) it appears the IDs are buried down in a long list after other items and entails hunting around.
Is there any way to restore the previous address/ID form detection behaviour?
This feature was never very reliable (and in my experience failed more often than it worked). Are you certain that there has been a change in behavior (i.e., is there a site that previously caused Identities to be previously displayed as Autofill Suggestion, but now no longer does so?)? It is possible that you were previously only visiting sites where the feature worked as intended, and now are visiting sites where the feature fails to work properly.
The option mentioned by @Nail1684 may be an acceptable work-around for you, regardless.
Yes 100%, I recall that my ID card was at the top of the list for several sites where I have to enter my email/street address details each time I use them, and now I have to scroll around to find the ID card entries. The feature worked well for me anyway, and the changed behaviour appears to be a regression. Indeed why does it have âcardâ or âloginâ type entries at the top of the suggested autofill list when there are no card or login entry fields on the page?
Also there are now icons when Iâm sure the vault entry types used to be in text, so this takes yet another step in considering what each icon means. Itâs no good having a âtidy, cleanâ UX if it forces users to have to stop and think their way through navigation.
If you have in fact enabled the option âAlways show identities as Autofill suggestions on Vault viewâ (under Settings > Autofill), then you should not have to âscroll aroundâ â unless you are on a web page that has a large number (>4â5) of matching login items. And if this is a page for entering address information, then it is likely not a login form; thus, you can get some relief by setting your URI match detection settings such that your login items only match when you actually have a login form open.
It would show login items in the list if you have kept the default URI match detection setting (âBase Domainâ) and if your vault contains login items for the domain you are on.
It would always show identity items in the list if you have enabled the option âAlways show identities as Autofill suggestions on Vault viewâ.
What do you mean by this? Can you post a screenshot that shows what you are describing?
Yes this option is enabled, but the id entries are indeed buried underneath card and login entries when they used to be right at the top. There are no login fields on the form.
I havenât changed any URI match detection settings - but the only one I can see is match base domain (recommended).
Hmm, so doesnât it detect the login fields (in order to auto-fill them)?
Either way the only thing that has changed has been the add-on version.
On one example I can think of there are login entries but for another part of the site, others donât have logins but still have the card entries above.
IIRC the entries used to be described via text, now they are icons. Iâll try to find a historical image, unless I can download an old add-on to test.
As you are on Firefox, you are on extension version 2025.2.0, as you wrote. This version still has login items as autofill suggestions, cards and identities (if set so) all together in the âautofill suggestionsâ section of the extension window, and it looks like this:
Extensions versions above that (I think beginning with 2025.3.0) have sub-sections in the âautofill suggestionsâ - not unlike the âTabâ tab of the old extension⌠and then it looks like this:
It shows that indeed the identity entries were listed under an âIdentitatenâ etc. text header whereas now those headings appear to be gone and one is left to decipher the vault entry type by icons alone. Fine for developers who stare at it all day long but not great for everyone else.
It seems my memory isnât so bad after all.
E2A: hmm, so from the last image, maybe the headings come back in newer versions?
Yup⌠Mozilla lags a bit behind, but will get that update⌠(the Chromium-based browsers already have extensions version 2025.3.0, whereas Firefox is still on 2025.2.0)
When you say âused to beâ, are you referring to version 2024.11.2, from over 4 months ago? If so, your recollection is not accurate, but at least some of your complaints make more sense.
It would be sufficient if you upload an image of what you see now (icons only, no text).
It detects the login field when autofilling, but not when deciding which vault items are going to be displayed as âAutofill Suggestionsâ.
The new version (2024.12.0 and later) does attempt to detect the presence of identity and card fields, and will shown those in the âAutofill Suggestionsâ section automatically, even if you have not enabled âAlways show identities as Autofill suggestions on Vault viewâ (this is still the case as of version 2025.3.0, at least on Chrome).
Letâs fix this for one of your address form webpages. Please share the URL of an address entry form where âthe id entries are indeed buried underneath card and login entriesâ, and show us a screenshot of what you see on the âVaultâ view of your browser extension when youâre on that webpage.
After we see what we can do with one problematic webpage, it should be clear how to proceed with the rest.
For the record, this is what it used to look like in version 2024.11.2 (for FireFox). As you can see from the screenshot, the identities were even back then âburiedâ below login entries and credit card items.
Hereâs what I see when purchasing postage from UK Royal Mail.
NB Iâm already logged in but the form asks me for my email address anyway. This is not unique to this site!
(Eventbrite is a pain for their event registration forms requiring info that is already in my profile.)
You can eliminate the display of the login item in the browser extensionâs âAutofill Suggestionsâ by editing the royalmail.com login item as follows:
Change the URL string stored in the âWebsite (URI)â field so that it reads exactlyhttps://send.royalmail.com/login (no more, no less).
As shown in the screenshot below, click on the icon located next to the âWebsite (URI)â field, which will toggle the visibility of a dropdown selector.
As shown in the screenshot below, click on the đ symbol to open the dropdown menu, and then select the option âStarts withâ.
Click the Save button in the lower left corner of the browser extension.
As mentioned by @Nail1684above, you will get subsection headings labeled âCardsâ and âIdentitiesâ once Mozilla releases the updated version of the browser extension.
You can also try to go to Settings > Autofill and disable (uncheck) the option âAlways show cards as Autofill suggestions on Vault viewâ. This will omit the credit card entries from the âAutofill Suggestionsâ area when you are not on a form that has payment information fields, thus reducing the amount of scrolling required; in theory, the card items are supposed to automatically become visible in the âAutofill Suggestionsâ area if you are on a web form that includes payment information fields â however, this may or may not work consistently for the websites that you use.
Another suggestion would be to mark the credit cards as âfavoritesâ (or at least the credit cards that you need to use for autofilling payment forms), and then disable âAlways show cards as Autofill suggestions on Vault viewâ. This will move the card items out of the âAutofill Suggestionsâ area at the top of the Vault view, and into the âFavoritesâ area that is located below your Identity items.
⌠I may be a bit thick in the head today - but independent of turning âAlways show cards/identitiesâŚâ on or off: one could also - if the inline autofill menu (Using the inline autofill menu for cards & identities | Bitwarden Help) is not unwanted entirely and could be used also - turn on:
Settings â Autofill â Show autofill suggestions on form field
and then: Settings â Autofill â Display identities/cards as suggestions
Tx, the issue with the above is that itâs just not scalable to perform on all sites that show the behaviour, and so BWâs default will have to stay.
The return of subsection text headings will help a lot in future in terms of ease of navigation.
Disabling âAlways show cards" helps a lot now. Will consider the other suggestions too.