This morning I was editing some entries in Bitwarden using my browser addon as usual. I got disconnected, then reconnected, and suddenly had the latest update.
Immediately I found that the ability to use the mouse to select text in Autofill URLs is broken. As soon as you click the mouse it begins to drag the entire UI element instead of selecting the text.
I’m hoping this is just a simple bug and not a terrible attempt to “improve” the UI.
Side note: Forcing a UI update on a user while they are literally right in the middle of using that UI is extremely rude. It caused me to lose work. Please stop doing that.
(PS: I had a similar experience as you @bmercer described with clicking the element and dragging it around… but as I tested it now again, it seems only be “draggable” as in the Release Notes written: when I click on that hamburger button (Chromium-extension in my case)… )
What may be even more serious - re-ordering the URIs seems to lead to loosing the set matching detection for that URI:
That’s quite serious, indeed. I would suggest making a pinned announcement in the forum to warn users not to re-arrange any URL fields if they use non-default URI match detection.
I am not a complainer, BUT this update this morning completely broke my ability to use BW in a FF extension. Clicked on FF toolbar bookmarks as always with the BW extension open and unlocked. See ZERO items to click on at all. My logins are almost exclusively in “no folder” and are alphabetical and that is how I like to configure it. After screwing around I was too frustrated to continue because my life is full ON today. Thank God I run on VM’s so I could go back and restore a snapshot from a few days ago. I broke the internet connection and then logged into the VM and set BW to NOT update ever for now. Went back online and its running great again, but this is a short term fix obviously. Wow would I have been frustrated to be running on bare metal and have taken the update without easy recourse. Love VM snapshots alot right now, LOL!
ps - running FF on Mint 22.1. I am pretty sure I can run with BW using the “old version” for quite awhile but what a surprise. I can continue to update this VM with BW updates locked so it will be easy for me to test any corrective BW release versions. There is not much risk since Snapshots always back my work up!!
Nobody in this forum thread works for Bitwarden or is responsible in any way for the code changes. All of us here (so far) are just Bitwarden users/customers, like you. If any Bitwarden staff should join this thread in the future, you will be able to recognize them by the blue-white shield logo overlaid on their forum avatars.
That is exactly what they implemented, and it seems to behave decently (other than the match detection bug mentioned earlier). If you click-and-hold the hamburger icon, you can move the entry. And, clicking in the entry behaves just fine to edit it.
The bit that went wrong is they broke editing URIs in vault items with a single URI. In this case, one can no longer drag-select text with their mouse because it instead tries to move the item, but with nowhere to drop it.
A third workaround would be to use the keyboard to select the text with e.g., Shift+Arrow right/Arrow left. After mouse click somewhere in the URI.
Ctrl+Shift+Arrow right/Arrow left would also work.
Tested on Windows 11. FF with Bitwarden Extension 2025.3.2.
That comment was solely related to your (subsequently removed) recommendation to add “a small tab or handle on the right side of each URL”. The newly added visual indicator consists of three horizonal lines (as indicated below) for entries with more than one URI.
The comment was not related to the drag-select bug, for which I did file a bug report (you’re welcome) in Bitwarden’s preferred venue.
Yes, I think that is what we all want, and how the in-progress fix (pull request) proposes fixing the bug. I don’t think any of us see value in adding a hamburger menu in the non-functional single-URI case.
I don’t see that on the basis of the current text we have (you mentioned, the OP was edited). Probably only @bmercer could clear that up.
I guess that was connected to the experience, that the thing moved around (= that must have been with a single URI). So, I read this as: when the thing moves around, then please add e.g. a hamburger menu.
As that was also under the assumption of OP, that that new behaviour could also be an unwanted UI change - and only hoped it was a bug:
So, I don’t see the clear demand to add a hamburger menu even with a single not-draggable URI.
Only this is indeed irritating, as it seems to not agree that the behaviour with one URI indeed is a bug:
… but I take that more as result of the slightly provocative exchange between you two , cumulating in an exaggerating inaccuracy one should not interpret too much into (as @bmercer in my view wanted only to emphasize that the thing still does move around, for whatever reason or circumstances - and no hamburger menu indicated that… I don’t think he really meant, he wants to have the hamburger menu, when it isn’t movable.).
)
) the temporary second URI.
, cumulating in an exaggerating inaccuracy one should not interpret too much into (as 