This is akin to the great Coke disaster
In response to the negative reaction, Coca-Cola reintroduced the original formula as “Coca-Cola Classic” just a few months later, in July 1985. The episode became a notable case study in marketing and consumer behavior, demonstrating the importance of brand loyalty and the risks associated with changing a well-established product. 
@Bitwarden: Get the old version back asap!
Hmm, nearly 400 posts on this one topic, far more than anything I’ve ever seen on any other topic.
I wonder what that could mean?
… and that was an example of people being overly nostalgic for a version of something that was worse. Coke had found that the new Coke was objectively tastier thanks to their testing, yet people preferred the old one not because of the taste but because it was marketed as different from what they liked.
I don’t think that’s likely to happen, but if you want you can get a UX that’s closer to the old one by changing a few settings: Usability issues (UX) in redesigned UI (2024.12.0) - #107 by FaviFake
Why wouldn’t it be ‘likely’? It solves all problems…
The workaround doesn’t work btw, I’m not getting the old UX.
Yeah that’s kind of a bait-and-switch. I don’t think anybody is falling for that at this point.
I don’t mind the new look, in fact, I sort of like the “Fill” buttton. HOWEVER, what I hate is that Identies no longer show up (unless, apparently, you are on a recognized login page). I don’t need my identify information on a login page, just the login info. But I need the Identity information when filling out an online form. If this is what their pilot groups liked, they are a bunch of dummies.
If you make your identities to “favourites” (edit → clicking the “star” symbol), then they get shown constantly in the favourites list, just under the auto-fill suggestions.
As a fellow user, for me that is first and foremost a kind of “support” and help to other users, to deal with the changes.
I also believe in trying to help and support other users. That’s why instead of pointing them at a setting that doesn’t actually bring back the old UI, I’ve been helping people sideload 2024.11.2, because that actually does so.
Thanks, this helped. I’ve personally sideloaded back to this version. Unfortunately, biometics integration is broken when sideloading but I’d do anything to get the old UI back, even if it meant accessing via passcode to unlock my vault 
The fill button is tiny. Please bring back clicking anywhere on the login card to fill.
It seems, the old auto-fill behaviour get’s back as an option:
I love how we have to mark certain items as favorites, just to get them to behave as they did before. I got an idea, how about JUST MAKE THEM BEHAVE AS BEFORE.
I don’t believe I have to go over every reason why a complete rollback of the browser extension is highly unlikely. In their countless contributions to the community, I think @grb probably has made the case somewhere.
You are not getting the old ux because that’s not a workaround, it’s a list of settings the developers have added specifically for those who voiced their preference for the old design.
I find it interesting that you chose to describe my contributions here as a bait and switch.
Side-loading an older version of a software that manages the most critical and sensitive information of a user means the program will no longer receive security updates.
If you truly wanted to support them, you would point them to the most secure solution, which happens to be the official one. The best option is not to sideload and older version of the extension, but to change password manager the one that is easier to use.
The best option is most likely to move to another platform. But that takes time. There are a lot of other password managers out there and features need to be assessed, as well as security, as well as usability, accessibility, etc.
And in the meantime, people still need to use Bitwarden. Sideloading the last good version provides that. What you keep suggesting does not.
Well why not. The new version is aweful. The solution is put the old version back and development a better one in the meantime.
I am not looking for ‘reasons why not’, which are excuses. I am looking for a solution.
We can spend months arguing the old UI versus the new UI (I prefer the old personally) but what strikes me as strange is that BW roll out a new UI, while they have over 600 unresolved issues on GitHub. Unless this new UI addressed all those unresolved issues, then BW are just adding to the list and frustrating their customers. If not rolling back to the old UI, then find a compromise that works for most.