Brave Browser worked fine with Bitwarden, Dashlane and Keeper. Maby try for your self 
see if it works
Vanadium is the same…
Can you please take this discussion somewhere else
2 Likes
Deleted by author
For anyone following this, I’d like to report that - at least for me - it has been resolved in the latest Brave update (1.65.114) which patch notes include:
- Upgraded to Chromium 124.
- Registered Brave as the autofill service for addresses.
- Added an option to disable autofill in private browsing mode.
To reiterate, I’m on a custom Android ROM and I’ve tested with multiple password managers that hadn’t worked prior to this update - no Accessibility Mode needed.
I still can’t get it to work, even with the latest version. I’m using Proton Pass.
Interesting, I have tested that one and it was working - that was also on the latest version of Graphene.
Credentials appear in the keyboard auto-fill zone, however nothing appears if the password manager is currently locked (Such as after a reboot or timeout).
AH, my apologies. In my experimenting prior to this update, I had enabled a special flag in Brave - and that combined with the update seems to be what allows it to work.
In brave://flags find #enable-autofill-virtual-view-structure and there’ll be a new “Autofill Options” in the General settings that allows you to switch from Brave Autofill to Android Autofill.
Bonus: If you want PassKeys to work, you’ll need to enable #web-authentication-android-credential-management as well.
7 Likes
I’m running Graphene with 1Password and Brave and haven’t had any issues with autofill working.
1 Like
Can’t reproduce, are you using google play services?
edit:
I finally manage to make Bitwarden autofill work in Brave without Gplay services; I had to set #enable-autofill-virtual-view-structure on enable without compatibility check.
4 Likes
Man I don’t know how I missed it last time but I’m glad I found it this time.
Careful reading on to do list as of now 