Fill button appears even if disabled on switching tabs
Steps To Reproduce
- Enable Click items to autofill on vault view
- Visit a site that can be autofilled
- Open extension and switch tab
- Switch back to vault
(It seems like it doesn't happen every time, might be a timing problem)
Expected Result
Don't show the fill buttons
Actual Result
Shows the fill buttons
Screenshots or Videos
https://github.com/user-attachments/assets/45fac0d2-2901-4725-81ff-a18761362397
Additional Context
No response
Operating System
Linux
Operating System Version
Arch Linux
Web Browser
Firefox
Browser Version
136.0.3
Environment Versions
Version: 2025.2.0 SDK: 'main (28c7e29)' Server version: 2025.3.0
Issue Tracking Info
- [x] I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
Thank you for reporting this issue! We've added this to our internal tracking system. ID: PM-19526
Hi there,
Thank you for your report!
I was able to reproduce this issue, and I have flagged this to our engineering team.
If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time - our engineering team will be happy to review these.
Thanks once again!
Good to hear!
I only found another case where it happens but I don't remember it and I guess the fix will apply to it too.
I'm seeing this issue as well but able to reproduce it under more simple conditions. When I opened my extension for the first time in Chrome I saw the fill button while Click Items in autofill suggestion to fill was already selected.
-
Open extension, fill button is visible, click to fill also works/is enabled
-
Untick and re-tick the
Click Items in autofill suggestion to filloption -
Fill button is not visible anymore
-
Close the extension window.
-
Reopen extension window, and fill button is again visible.
Operating System Windows 11
Operating System Version 22621.5335
Web Browser Chrome
Browser Version Version 137.0.7151.69
Environment Versions Version: 2025.5.1 SDK: 'main (c6835e5)' Server version: 2025.5.2
I am experiencing the same issue.
I can reproduce what @JoshMart describes - though it indeed doesn't even involve switching tabs in the extension as @D3SOX described initially, but it is enough to just open the extension window:
https://github.com/user-attachments/assets/478dac5e-ab6d-4f76-832d-7ea9126f0f91
Seeing the same issue as @JoshMart and @pamperer562580892423 describe here on my computers. Two different computers and multiple Chrome profiles.
Windows 24H2 Chrome 137.0.7151.104 Bitwarden extension Version: 2025.5.1 SDK: 'main (c6835e5)' Server version: 2025.6.1
I have this same issue, I don't need to switch tabs. I just need to click on the extension icon in chrome's status bar and it shows me the fill buttons and I have the option selected where it should not do that
Can you please stop it with the "I have the same issue" posts? I think we already have enough information here and I would like to be subscribed to receive actual updates.
Can you please stop it with the "I have the same issue" posts? I think we already have enough information here and I would like to be subscribed to receive actual updates.
@D3SOX Especially if you indeed meant "the exact same issue" shouldn't be reported here any longer -- if the exact same issue would be opened as a new "bug report" here, this would be closed as a duplicate.
So, it would be the intended approach, if one indeed experiences a "same issue", to join in on an existing bug report instead of opening a new one (which would get closed as a duplicate).
What kind of false dichotomy is this? If you have nothing productive to contribute, don't post anything, no duplicate issue, no unnecessary post. You could use a reaction.
Though I also think it would be more productive to post also some details (like exact versions, descriptions of the issue especially when it's (slightly) different, screenshots/videos etc) than just "me too" - even to convey that others experience the same bug, and it's not only a "singular exception", can be helpful for BW to get a more broad picture of the issue.
And this is a public section here - if you are annoyed wirh notifications, then cancel the subscription and have a look from time to time. And chat with BW support the next time - that is more private.