Firefox auto updated the addon…
Now it fails to offer fillings when clicked into box:
when I click Fill in addon window it correctly recognises we have entries
I’m not talking about auto filling.
Version 2024.12.3
Why break something that worked perfectly.
@notmypassword4566 It doesn’t seem that your post has anything to do with Client Localization (the forum category that you had selected), so I’ve moved it into the Section of the forum that is for Password Manager issues.
Please share the following information:
In addition, in the browser extension window, please go to Settings > About > About Bitwarden and post a screenshot of the information shown there.
Does it fail with every one of your associated vault items? Or just with some? If the latter: do you have a (harmless) example domain to check it?
Sidenote: That version is heavily outdated. I guess the current Firefox version is 134. If only for security reasons, you should update that.
Troubleshooting of problems will absolutely depend on the environment (OS, browser, extension version, server, etc.).
Therefore, I would appreciate if you could follow my instructions from above, and take the following action in the Bitwarden browser extension UI:
You will find the 
Settings button in the bottom right corner when you first open the browser extension window:
Bitwarden browser extensions were upgraded to MV3 starting with version 2024.5.0, but Firefox support for MV3 did not arrive until version 109.
Sorry you mean that menu, I can post it on Monday, otherwise the version displayed in extension manager “2024.12.3” should be enough to identify the version.
But the BW dropdown menu is shown (this would be the env dependent part),
it is just not populated by BW (no items found).
Does it work for you?
The screenshot will also have information about the server you are connected to.
The Bitwarden code base contains a half-million lines of code, and the architecture of the browser extension code in particular is very complex due to MV3 requirements. I don’t think either of us are qualified to make predictions about how the code would behave if installed on an old MV2 browser.
I can’t help you with that, as I don’t use those inline menus at all. I could enable them to check for you, but in my Firefox browser, I have left the browser extension on version 2024.11.2 for testing purposes. If you provide a URL to check, I could try either in Firefox with version 2024.11.2, or in a Chromium-based browser with version 2024.12.4.
Sorry for the delay, the version with the issue:
Why not just put MV2 addon on a branch with only security/compatibility updates for N years.
Less work supporting both in new version.
Also the “update entry” box seems to fail to show up (on http POST?).
Which is problematic since it provides password suggestion, but it fails to save it.
In changelog I don’t see a clear indication which was the last MV2 version
https://addons.mozilla.org/en-GB/firefox/addon/bitwarden-password-manager/versions/
@notmypassword4566 No offence, but why even use a Firefox version (104) that did not get any security updates for longer than the last two years? (Firefox 104 was released in August/September 2022)
I will stick to Firefox ESR as long as possible, because I’m more productive on non AI/ads/spyware filled new OS versions, and I never had any viruses for +20years. It’s not for everyone.
I’m happy with MV2 addon as long it’s compatible with the server.
Then think about changing to the current Firefox ESR 128.6.0.
Puh… All off-topic now, but a) single instances are never that good of an argument 
and b) outdated software with security vulnerabilities always pokes holes in your security, not only for “viruses” but also for any kind of malware etc.
And, probably a bit back to the topic - incompatibilities regarding features also get more possible with outdated versions.
