Given the alternative (not having the ability to change the state of the checkbox at all), I don’t think that those users would grumble too much…
The new default should apply only to new installs. Anyone currently using the extension should not experience any change. It really would make everyone happy.
No idea why choice was removed in this case. Baffling.
2 Likes
@dwbit i agree with @DenBesten and @grb’s opinion from this thread and from the linked one (✅ Make "Click items to autofill on Vault view" the default - #7 by grb): I DO NOT WANT click to autofill. I want the ‘Fill’ button.
I believe removing that option is the WRONG choice and i would like it brought back please.
4 Likes
Yeah, it seems that new feature went live now…
From when I started using Bitwarden, I was annoyed by the different behaviour when clicking an item. Apart from all it’s possible flaws: I liked the “Fill” button much more than the inconsistent behaviour.
Especially taking away that choice itself is very disappointing, as others also pointed it out. Everyone would have been able to revert the new default for themselves again then.
(though, personally, I could imagine that the coding effort to support two different sets of behaviours might have also played a role in this decision)
As a dev, i can’t understand what coding effort is there.
In my mind this should be almost as simple as:
- a boolean config + some trl strings
- on click do an
if(config==autofill) then autofill else open the row
not that much code to maintain
2 Likes
@TheBestPessimist The choice itself probably is very simple.
I had bugs/issues like this one (Fill button bug · Issue #13108 · bitwarden/clients · GitHub /// Fill button appears even if disabled on switching tabs · Issue #14000 · bitwarden/clients · GitHub) in mind. Seems to me like keeping a consistent behaviour for both choices/variants might be more complex than just a boolean, when other things are changed in that whole context.
Anyway, I would like to have that choice myself again.
The new Autofill-by-Default behavior is infuriating. Why does BW insist on messing with its customer base? Are your PMs bored? At least give us a setting to disable it!
Exactly!
2 Likes
There is was such a setting, but it was removed in version 2026.4.1. Some of the code still exists, and it seems that all they really need to do to fix the problem is to roll back whatever PR removed the setting, and then change the value false to true in two locations of the code (to satisfy the complaints that presumably motivated the removal of the setting):
4 Likes
Just wanted to add one more user’s voice to this conversation. I just opened a support ticket 2 days ago to try to formally complain about the new change in Version 2026.4.1, that users cannot alter the setting on what clicking an Autofill Suggestion Item does, either to View or Fill. I have no idea why the Bitwarden team made this change, seemingly on purpose, as I feel taking away customization options that were already implemented into a software is almost always a bad idea. From reading the above posts/replies by more informed users, it seems like the code to revert this change would not be much work on behalf of the Bitwarden team. I don’t know enough about coding to have an informed opinion, but if that is true and honestly even if it isn’t easy, I sincerely hope the Bitwarden team reconsiders the philosophy they might have of “simplifying” the software/browser extension and adopts a different philosophy of clean design but retaining user customization.
Please reconsider re-adding the setting “Click items in autofill suggestion to fill” or add a different setting for “Click items in autofill suggestion to view” if the Bitwarden team would like to keep the default as clicking autofill suggestion items to fill.
1 Like
Hi there. I have been a bitwarden user of 2 years and am absolutely appalled and infuriated by this update forcing auto fill as the new default option when clicking on a login.
In August 2025 clickjacking was revealed to be a serious security concern, and is one issue bitwarden never fully fixed. Since that issue, thousands of us have starting using copy paste rather than autofill to protect ourselves. This update makes the default behavior to autofill - which is really insecure since clickjacking is virtually impossible to detect even for sophisticated users.
PLEASE revert this update. If autofill is turned off in settings, then the default behavior of clicking on an item should be to open item details, and NOT to autofill it. Autofill as default behavior is insecure, and at a minimum should only apply to users who have autofill turned on, which a huge amount of us do not.
When can this be fixed? IMO this is a dealbreaker for those of us aware of the clickjacking issues that were never fixed. We do not want to move to a different provider, but we will.
1 Like
Noting there was a Reddit thread about a click-jacking issue and reverted click behavior recently:
1 Like
@Reabsorb4-Headband Welcome to the forum!
Just a sidenote to clarify on this one – Bitwarden considers a whole bunch of different autofill options as “autofill”. You can’t deactivate autofill as a whole. In the settings of the extension, you can deactivate the inline autofill menu and autofill on page load or autofill via the context menu. But e.g. autofill via keyboard shortcuts and via clicking items (as we mourn the loss of the Fill button) can not be deactivated.
YES. BRING BACK THE FILL BUTTON. This is really insecure and frankly I’m going to cancel my subscription if this continues to be an issue.
Welcome, @zfJames to the community!
In what sense do you view this as insecure? To use click-to fill, one must first be on a web page that matches a vault entry, then open their vault, locate the entry in the “autofill” section and click on it. There are plenty of steps required with click-to-fill that the user is well aware that they are accessing a credential.
The clickjacking risk mentioned in the above reddit thread is more about a webpage having a button labeled (e.g.) print that in reality submits a credential when the user expected to be printing the page. This concern is primarily related to inline-autoflll (which one has the option to disable) and autofill-on-page-load (which is disabled by default). Click-to-fill, Drag-and-drop, and keyboard shortcuts are largely not susceptible to clickjacking.
Click-jacking may not be relevant to these methods, but autofilling techniques such as click-to-fill, keyboard shortcuts, or the right-click context menu are all susceptible to info-stealing by invisible form fields (either deliberately implemented by otherwise legitimate websites that wish to maximize harvesting of user data, or via hidden forms injected by advertising or analytics services, or a result of server-side compromise). Thus, some users prefer drag-and-drop or copy-and-paste (even though the latter method has its own associated security vulnerabilities).
Having now lived with version 2026.4.1, I can confirm that the UX is significantly degraded due to the decision to eliminate users’ ability to configure one-click item viewing.
A significant pain point is accessibility of data in card and identity items. As I previously explained in December, 2024 (which is when users first lost one-click view access to cards and identities), this is a problem:
There are many other use-cases in which viewing a vault item has higher priority than autofilling, so removing user choice in the name of “simplifcation” is (IMO) shortsighted.
For context, prior to v2024.12.0, cards and identities used to have their own dedicated (but optionally displayed) sections on the “Tab” page (default home page for the browser extension), with a one-click “View” button. This was great.
With the 2024/2025 UI-redesign, the “Tab” and “Vault” views were consolidated, and autofill suggestions became click-to-view (with a “Fill” button for autofilling), but Cards/Identities became hidden (i.e., unclickable) — except for when Bitwarden’s imperfect detection algorithm determined that there were payment or address fields on the web page. This was the subject of a feature request, which was ultimately addressed in v2025.2.2, by introducing the options to always show cards and/or identities as autofill suggestions (not in their own, dedicated sections, as in the pre-2025 UI). This solution was (IMO) clunky, but at least it restored one-click view access for card and identity data.
Unfortunately, with v2026.4.1, even if one has enabled the options to “Always show cards/identities as autofill suggestions”, it is now necessary to perform an extra click (on the “More Options” button), and a scroll to the top of the context menu, before one can click “View” to view the item details.
As a work-around, I have been forced to disable “Always show cards/identities as autofill suggestions”, add the cards and identities to my “Favorites” section, and then rename all favorited items to insert a numerical prefix (to create separate groupings of logins, cards, and identities within the “Favorites” section — albeit without headers for the subsections). This is ugly, inconvenient, and still a UX degradation, but at least it makes possible one-click access to the item details:
3 Likes