I am writing to urge a design overhaul regarding how vault items behave when clicked. Currently, across the Windows Desktop Application, the Web Vault, and the Browser Extension, clicking the main text name or URL of a login item opens the View/Edit panel or popup instead of launching the website.
This behavior goes entirely against universal web design conventions. When a user sees text styled like a website link, the immediate expectation is that clicking it will navigate to that destination.
Why the current implementation causes severe user friction:
Tiny, Fiddly Targets: Forcing users to aim for the microscopic Launch icon is incredibly tedious and heavily prone to accidental misclicks—especially on high-resolution Windows displays.
Destructive to Auditing Workflows: When trying to pass through a large vault to clear duplicates, update weak credentials, or check if websites have added passwordless support, the current layout is painful. In the Web Vault, clicking the item triggers a massive center overlay popup that completely blocks the background vault list, forcing the user to constantly close the modal, lose their place, scroll, and repeat.
Inconsistent Across Clients: The extension behaves differently depending on whether you click a matching tab suggestion or an item from the main list, adding to user confusion.
Proposed Solution:
Make the text a true link: Clicking the primary URL text string should instantly launch that website in a new browser tab.
Separate the Edit Function: To view details or edit an item, users should click a dedicated pencil/edit icon or click an empty space on the row card that isn’t the text link.
Please consider updating this interaction model. The interface should help streamline our security workflows rather than creating unnecessary hurdles to just opening a website.
Nevertheless, I’m going to close this request (with some delay for further discussion, if necessary) as feature requests have to be about (more or less) one specific thing only.
Otherwise, it’s not possible to interpret any votes. (and simple example: if a request would be about a feature A and a feature B, how should someone vote who would be in favour of feature A, but doesn’t want feature B under any circumstances? – But, in general, there are also other considerations like not mixing up several topics in one “discussion”/request, avoiding duplicates of feature requests, …)
So, please feel free to open new separate feature requests about one specific thing only each. (and please search for possible existing feature requests, that may match your requests, first)
Autofill the credentials in the underlying web page (FR)
Launch the (first) website associated with the vault entry.
Also, do note that there is no URL on the vault tab, although one might set the vault entry’s name to look like a URL (which Bitwarden does by default).
And, there is currently a vigorous debate as to whether #1 or #2 are the best option. Since you now have proposed #3, let’s see how many votes this one gets .
As the OP mentions clicking on a vault item and it displaying “view/edit”, I believe they are referring to clicking on “bitwarden - community ” in my picture above. None-the-less, clarification would be useful as @Nail1684 has clearly demonstrated that the intent can be interpreted in a few different ways.
I agree this would enhance Bitwarden’s usability. Making the URL open directly feels intuitive, while separating View/Edit actions would expedite bulk vault reviews and credential audits, particularly with large entry lists.
For clarification, the attached screenshot highlights the two elements involved in this request.
The login item title is highlighted in yellow, while the current Launch button is highlighted in magenta.
My suggestion is to allow the larger title area (yellow) to perform the same website-launch action that is currently available only through the Launch button (magenta).
@Schanibel Ah, thanks for clarifying this. I’ll adjust the title and may edit or remove some of my posts then to clear your FR up.
Could you edit your first post to remove the reference to URLs? You are indeed talking about the item title – and that does not need to be a URL, so that only causes confusion.
(If you can’t edit yourself, would you be okay with me editing your first post accordingly?)
@Schanibel One question to your request itself then: only login items do have an associated URL so that a website can be opened with clicking the item.
Cards, Identities and Secure Notes don’t have a URL, so if your request was implemented this probably would create an inconsistency with clicking items – and what would you suggest should happen if a Card, Identity or Secure Note is “clicked”?
PS: Personal thought: maybe requesting customization for the clicking behaviour would be another possibility to solve this in a way that would make everyone happy…
Yes, please go ahead and edit it accordingly. I agree that referring to it as the item title rather than a URL will make the feature request clearer and avoid confusion.
.
” in my picture above. None-the-less, clarification would be useful as 
