- cross-posted to:
- [email protected]
- [email protected]
- cross-posted to:
- [email protected]
- [email protected]
Ah, so it isn’t just me. I had noticed this myself recently.
And I thought to myself that Bitwarden was aggressively forcing users a pro-security measure.
Yes, it’s been going on for a while and it’s really annoying.
10 days ago:
We have identified the root cause of this issue and the fix will be included in the next release of the Firefox extension. I can’t commit at this point to a date for that release, but the issue has been identified and will be included.
https://github.com/bitwarden/clients/issues/8873
I remember waiting for a similar fix in the past and it took Firefox ~2 weeks to verify the new version.
I thought it’s a feature.
The best bugs are undocumented features.
I noticed that this morning for the first time. I was wondering why this happened. Had the Ctrl shift L stop working too.
Weird, not happening on any of my machines , mac and Linux.
I think this bug also hoses my Firefox unless I have Bitwarden disabled.
I noticed this and the fact that
Ctrl + Shift + L
no longer autofills. That was my favorite feature but for some reason it has stopped workingThat was a Firefox bug, based on one comment in the Bitwarden isue tracker . It should be fixed now in Firefox 116.
Had that happen a couple times over the last months. De-and-Reactivating the plugin worked for me
Damn, you gave me hope but it didn’t work :( I’ll have to do some searching for a solution. Up until now I’ve just accepted it as an annoyance
could also check if the shortcut is still set. I’ve seen people who had that suddenly reset to blank for some reason.
It was a bit annoying to fix, in the end. But the feature itself is still there, just a bit buggy when an update is distributed
Why should I trust anything on .ml?
That’s pretty much the main reason I migrated to proton pass… was bugging me for a year I think