Which Bitwarden app is your issue or question about?
1 - Browser Extension
Bitwarden App Version
2026.10.2
Operating System
03 - Windows
Where is your vault hosted?
Bitwarden (default)
Description
I’m using Firefox 160.0.1 on Windows 11 with the Bitwarden Extension, 2026.10.2. Firefox was updated to 160.0.1 today.
After the update, I tried to login to a site with a passkey but FFx appeared to timeout. I tried another site and had the same experience. I was able to login to both sites with no problem on Vivaldi.
After filing a report with Mozilla, I closed FFx, but I noticed the taskbar icon still had a little line under it, indicating an open FFx window. Hovering over the taskbar icon, I saw a thumbnail Bitwarden extension window, appearing to ask me to approve the passkey for the site I was trying to log into.
I clicked “X” on the thumbnail, then restarted FFx. It opened at the same size as the normal BW extension pop-up. I resized and tried to login to a site with a passkey and I saw the same experience, but when I hovered over the FFx icon in the task bar, I could see the BW thumbnail, so I right clicked and chose “Move,” and the BW extension window was visible. I was able to confirm I wanted to use the passkey and I was logged in.
I have a dual monitor setup and FFx normally runs in the “second” monitor. If I move FFx to the primary monitor, then the BW extension pop-up is over the FFx window.
When I leave FFx in the secondary monitor, when I’m expecting the BW passkey pop-up, if I hover over the FFx icon in the task bar, right click on the thumbnail for the pop-up and choose “move,” and press the right arrow, then the pop-up will be under my mouse cursor, which I can move into view.
As an experiment, I clicked on the BW extension button in FFx and clicked the icon to have the extension “pop out” into its own window. This has the same behavior–I have to right click the thumbnail, choose “move,” press right arrow, then drag the pop-up into view.
I’m guessing this is something that Mozilla changed in FFx 160.0.1, but I don’t understand why it’s affecting the BW pop-ups in this manner. I looked at the release notes for 160.0.1 (and 160.0.0) and nothing appears to be related to this.
Anything we can do to resolve it? …thanks!