mirror of
https://github.com/actualbudget/actual.git
synced 2026-07-11 09:32:33 -05:00
[Bug]: Does ActualBudget not support Bitwarden Chrome Extension overlays? #2654
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#2654
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @thecodygriffin on GitHub (Nov 25, 2025).
Verified issue does not already exist?
What happened?
It appears that Actual Budget does not support the Bitwarden Chrome extension. The icon doesn't appear in the password field and a "refused to connect" over lay appears.
I believe it is because Actual Budget has relatively strict cross origin policies.
Cross-Origin-Opener-Policy: same-origin
Cross-Origin-Embedder-Policy: require-corp
Is there anyway to mitigate this issue?
How can we reproduce the issue?
Where are you hosting Actual?
Docker
What browsers are you seeing the problem on?
Chrome
Operating System
Linux
@youngcw commented on GitHub (Nov 26, 2025):
You should only need to login once so it's not a big deal to copy the password then paste it in.
@thecodygriffin commented on GitHub (Nov 26, 2025):
I found this issue for the Bitwarden Chrome Extension.
https://github.com/bitwarden/clients/issues/17649
I am not sure if ActualBudget is being too restrictive with its XSS policies or if the Bitwarden Chrome Extension has a bug. I tend to think it is the latter.
When I first deployed ActualBudget back in June 2025 on 25.6.1 and I do not recall it being an issue then. Now when I deploy a 25.6.1 container, the issue is present.
@matt-fidd commented on GitHub (Nov 29, 2025):
I imagine this is more to do with the linked bitwarden bug than Actual, I can reproduce on latest and older versions with bitwarden installed. I'll close this off, as it's not really an Actual bug as far as I'm concerned, but others will hopefully find it if they search for it.
If you can't get rid of that overlay, open the extension settings, go to settings -> autofill -> and toggle "show autofill suggestions on form fields" off and on again.