2025.1.0 / 2025.2.0 Browser Extension UI/UX Megathread

I don’t understand how the new browser UI passed any kind of quality control check. Tasks that used to be simple are now burdensome. There are numerous examples I could point to but I will suffice with just 2 examples here:

  1. Not wanting a small fill button for something that used to not require an extra button taking up space, I disabled the fill button. But now I am stuck with this kind of nonsense: when wanting to populate credit card information, in the old UI I would simply click the rectangle. In the new UI I have to click 3-dots and then auto-fill.

  2. In the old UI when I wanted to create a new custom TEXT field, I would click the button to add new a new field and then I could fill out the Title and the Content without clicking anything else. In the new UI, I now have to needlessly click to create the Title field and then click again to create the content field. On top of this, the font and styling in the new UI is so big that I constantly have to scroll just to accomplish these basic tasks. No scrolling at all was necessary in the Old UI. This is just plain bad design!

Further, when creating Hidden content, the old UI would stay on in Hidden configuration mode so I could immediately create another Hidden field. The new UI forces a new click to create another Hidden field.

This new UI is among the worst designed interfaces I have encountered and it is a huge burden to interact with on a daily basis.

Bitwarden, how about reverting back to the OLD UI and doing your customers a good thing. Please?

2 Likes

Since extension version 2025.1.3, if you turn on “Always show cards/identities as Autofill suggestions on Vault view” (Settings → Autofill), cards and identities should get auto-fill functionality back.

They basically delete most of my posts at this point, including my previous reply, but as I pointed out a few minutes ago, if they have not reverted to the old UI by now, they aren’t going to. The best thing to do is move on to a different product. Can’t stay on the old unsupported version forever.

Actually I can’t disable the Chrome password manager. Chrome is telling me that Bitwarden is “controlling this setting” so it’s greyed out and I can’t change it.

Sorry, I misunderstood your original comment. This is a bug, but it can be solved as follows.

Disable “Make Bitwarden your default password manager”, then uninstall the Bitwarden extension and reinstall it. Refrain from enabling “Make Bitwarden your default password manager”, and if you see the prompt below when making changes to the autofill settings, make sure that you always click Cancel:

 

This should allow you to disable the Chrome password manager under chrome://password-manager/settings.

What is up with Firefox having a 2 month old version in the official addon store?
Good idea to just install from the latest xpi off Github?

Firefox always lags behind. No clue why their store’s approval process is so much longer than the others, but I do agree that 2 months is much longer than the typical delay.

This is just ridiculous on their part if there are any security issues that need to be addressed asap.

I’ve tried to be patient with the new update and I appreciate bringing back some of the most critical features, but I still find myself frustrated sometimes with everyday use. Here are some requests that would help bring some satisfaction back to a premium user:

Improved Search :magnifying_glass_tilted_left:

  • Single word search should sort by “starts with…” first
  • Multi word search should use AND filtering rather than OR (or at least the option to match ALL words (default) or match ANY word)
  • Multi word search should sort the items that match the whole phrase first
  • Include Note content in search
  • Option to flatten search results to single list rather than filtering the “Autofill Suggestions” and “All Items” separately

Default Launch Website :link:

  • When clicking a login item that does not match the current page, the default action should be to launch the website in a new tab, not view it.
  • 99% of my extension use is either filling a current page’s credentials or searching my logins to open a new site
  • This would pair nicely with keyboard navigation

Keyboard Navigation :keyboard:

  • Allow keyboard navigation using arrow keys and enter for default click action (I know this wasn’t in the old UI, but this was the biggest feature I still miss from LastPass and I imagine you could win some good favor from your power-users)

3-Dot Menu ⁝

  • Add an Edit option to the menu
  • Menu should always include View and Launch options despite what the default click action is or if the option is available as an icon

Adjust Extension Height :up_down_arrow:

  • Either dynamically with drag or in settings (e.g. a % of view height)

Universal Login :unlocked:

  • If I’m logged into the desktop app, I should be automatically logged in to my browser extensions
  • On a given day, I probably use 4-6 different browsers or browser profiles, so only signing in once would be great.

Show Card Exp Date in List :credit_card:

  • For the few occasions that the card autofill doesn’t work, I appreciate that I can copy the card # and the CVV, but then to get the Exp. date, I have to view the item.
  • Maybe add the text (mm/yy) to the subtitle
    image

Pop-out Individual Item :left_arrow_curving_right:

  • Add an option (probably to the 3-dot menu) to Pop-out View an individual item

Note Modifications :spiral_notepad:

  • Put the copy button in the top corner and move the scroll bar to the edge.
  • Or auto-expand the note area to match the content…not sure we need a scrolled window within another scrolled window.

@mikerowe81 Welcome to the forum!

Your requests are reasonable, but to be clear, all of these are requests for features that also did not exist in the old UI.

By using the forum search feature, you will be able to find existing feature request for many of your suggestions, and if some of your ideas do not have existing feature request threads, you should consider opening your own feature request topics — we just ask that you open a separate feature request thread for each proposal (i.e., propose only one new feature per topic).

Thank you, this worked.

1 Like

@dwbit, are you still reading responses to this thread, or has it by now gone old?

I see a number of commenters praising the new layout; I’m sorry to say I for one pretty much hate it.

WHY did you make the default action when clicking on a password entry “view” rather than “auto-fill”? I don’t know how you do your metrics, but I would have guessed that “auto-fill” was BY FAR the most commonly used action.
image

Then when you do click “view”, it’s another click to “edit”. I hate this. I MUCH preferred the old way where a click (pretty nearly anywhere) would auto-fill the credentials, and you could enter edit mode with one (more careful) click.

Another thing is the “copy” button (My browser pop-up doesn’t look like Nail1684’s images) - what does it copy? Why do you not show the “copy username” and “copy password” buttons that you used to? I now need to make so many more clicks to open a profile, copy the username, paste it, re-open the profile, copy the password, and paste that. Bravo, UX team…

Sorry to sound like a grumpy old man.

1 Like

@noughtnaut Welcome to the forum!

The why-question may find an answer e.g. here ✅ Consistent behaviour on clicking a listed item in vault - but if you don’t like it, you can change it back to the old auto-fill behaviour: Settings → Autofill → Click items to autofill on Vault view

I too would like to have the “Edit” option in the three-dot-menu on Vault view…

No, you don’t: Settings → Appearance → Show quick copy actions on Vault

:wink:

1 Like

Oh, this is so much better. Ahhh. Thank you so much!!

1 Like

@noughtnaut, welcome to the forum!

You might review the first post in this topic periodically. @dwbit has been updating it as features frequently requested in the topic are implemented.

Awesome, thanks… Maybe not what I asked for, but exactly what I needed.

1 Like

@gently4575 Welcome to the forum! (and Sorry for the delayed answer)

Because you wanted a “more recent” extension version, Mozilla did not approve yet? - Because otherwise, Mozilla’s add-on store would be fine to install the extension.

I think I wrote recently, the following: sometimes, Mozilla takes a few days to a week until they approve/“release” an updated extension. Mostly it’s about 1-2 weeks. And sometimes it’s even about 3 weeks or longer, as we see it now.

But it’s not exactly two months at the moment. Out of curiosity, I recorded it the last weeks :sweat_smile: : Mozilla approved the extension version 2024.12.4 on Jan 14, though their store shows the release date of the extension itself (by Bitwarden on GitHub), which was Dec 27, 2024. I took that screenshot on Jan 14:

So their “last updated” could be perceived as slightly misleading (or not!) as it shows the release of the extension itself - and not when they (Mozilla) approved/released it.

Patience… in the end, there will always be the next update… Though I understand the frustration, that the Firefox extension almost always arrives the latest, due to Mozilla’s review process.

I get that as a general message, but since your response was also to me, I would like to add, that I’m just another customer and not a Bitwarden employee. :wink:

Hello @nail1684 and thanks for the welcome. So far Mozilla has not published any of the 2025.1.x branch, and yes I agree with you the AMO web page and your screenshot can look misleading but it does prove that Mozilla are picking up the BW GH releases as they happen. I really don’t know why Mozilla do that and create trouble for themselves but you know, Mozilla :stuck_out_tongue_winking_eye:. Head over to the Mozilla discourse and add-on approval, even for private add-ons is a constant source of grief for add-on publishers.

The reason I wanted a newer release is because the newer release works without significant lag. Not a version number fetish. After all I was regressing the whole browser in order to get it. The patience that I required was not in waiting for a new release of the extension in the AMO but the patience I required every time I used the BW extension in FF. The 2025.1. x branch was much improved The 2025.2.x branch is nearly as fast as the Chromium extension and perfectly acceptable.

So… I wanted an extension which works on a supported version of the browser which did not leave me at the mercy of Mozilla’s seemingly slightly chaotic approval process. Or I could just use a Chromium based browser like 98% of the population and it took them 6 days from the release 2025.2.0 to its updating in Brave through the Chrome store.

So, it’s not BW’s fault, not mine and not yours. Updates security related extensions minimise support efforts and are generally a good idea as I understand it. What is the problem, if any?

Firstly, massive thanks very much to the Bitwarden team for working hard on these improvements.

Regarding compact mode, I’m a big fan of the way it compacts things vertically. However, one major issue with the update (on Firefox at least) which I’ve not seen anyone from Bitwarden address is the minimum width of the sidebar. The old version would allow you to make the sidebar as narrow as you’d like, and you’d still retain full functionality. With the new version, you lose access to the buttons unless you have the sidebar pretty wide, which is a pain for those of us who frequently have the sidebar open. It would be ideal if the compact mode would also allow for a more compact view horizontally, maybe by using ellipses to hide part of the item name and username on narrower screens. It would be amazing to get full functionality back!

Please Fix “Always Show/Cards Identities” (Remove From “Autofill Suggestions”):

In case Bitwarden devs/product design staff are still trawling this thread for feedback, here is a major annoyance that I just discovered:

I was a supporter of the request to restore the ability to permanently display cards and identities on the Vault page, and did voice misgivings about the design decisions implemented in PR #13068, which made the permanent Cards/Identities sections subordinate to the “Autofill Suggestions”.

Not only does this stymie efforts to campaign for a much-needed function to collapse the Autofill Suggestions section (to prevent it from getting in the way of search results), but now I just discovered that even with “Always show Cards/Identities” enabled, the card and identity items completely vanish from the Vault page if you pop out the extension window.

It was a conceptual mistake to associate the “Always show” options with the autofill function, because a major reason to want the cards/identities permanently accessible is for use-cases that do not involve any autofilling (for example, reading the information over the telephone).

When I have time, I will post a feature request, but I wanted to first raise the issue in this feedback thread, in case it is still being followed by anybody who can take action. (On that topic — I see that the opening for a new Director of Product Design appears to have been removed from the Careers page recently; hopefully, that is good news for all involved…)


Edit: Missing quotation mark in title.

1 Like