• Off Topic

  • Inline Autofill and Vanadium (Chrome)

I have been assuming that something is wrong with Bitwarden and Chrome-based browsers, particularly Vanadium, but after testing some things out I have deduced that Chrome browsers on Android don't seem to play well with autofill.

I was very excited to read that Bitwarden had added support for Vanadium. On one of my devices with GoS I was running Vanadium (org.chromium.chrome) but inline-autofill was not working. I decided to take a second device and do a fresh install of GoS so that it would have a package name of app.vanadium.browser, which this github issue tracker specifically states support for.

I've tested various Android browsers' autofill ability using Bitwarden and KeePassDX.

Within GoS at Settings->Passwords & accounts->Autofill service I alternately selected Bitwarden or KeePassDX form autofilling, depending on which password manager I was testing. Inside the Bitwarden app at Settings->Auto-fill I have Autofill service and Use inline autofill enabled. Regarding inline autofill, I am using Gboard with network permissions revoked. Similarly, inside the KeePassDX app at Settings->Form filling->Autofill settings I've enabled Inline suggestions.

With these settings, neither Bitwarden nor KeePassDX inline-autofill work for:
-org.chromium.chrome (Vanadium)
-app.vanadium.browser (Vanadium)
-com.opera.browser (Opera)


Bitwarden/KeePassDX inline autofill does, however, work with com.vivaldi.browser, though there are apparently some modifications to its Chrome base.

All Firefox-based browsers that I tested (Tor Browser, Firefox, Mull) work splendidly for autofill using both Bitwarden and KeePassDX.

Many apps on my phone do not work for autofill and I can only assume that these apps are Chromium-based, although that's just a guess.

This issue is a huge problem IMO and I'm wondering if anyone out there has any insight into what the outstanding issue is. Is this an AOSP thing? Chromium-base thing? GoS thing? Bitwarden/KeePassDX thing?

6 days later

Bitwarden is working just fine on my device (6a) with every app including Vanadium. I have all four options turned on in Auto-fill services in Bitwarden settings.

    KeepassDX also recently added the Vanadium compatibility for auto fill, but still it does not work for me and I don't know why. Good to know that at least Bitwarden works..

      digital As stated above, that's because native auto-fill feature doesn't work in Chromium browsers. It's nothing specific to Vanadium. Changing the code in KeepassDX isn't going to rescue that. Bitwarden only works if you enable all sorts of invasive auto-fill features, which I'm not willing to do.

        daffy
        I enabled all four options just to test, Bitwarden still does not work for me

          Yes, in Chrome on Android, Google did not implement full support for third-party auto-fill functionality, and luckily it is fine on desktop version. I doubt Bromite or Vanadium can do this kind of support on their own.

          By the way, does anyone know how to export bromite or vanadium's history into one file? Thanks

          4 months later

          Setup KeePassDX just to find out it is not working on Brave browser.

          10 months later

          It seems that Vandium inline autofill started to work with Bitwarden.
          You need to enable 'Use other providers' in Vandium Autofill options.
          But not able to find autofill entry in Bitwarden automaticaly. Need to search it. It is an additional step.

            andonl But not able to find autofill entry in Bitwarden automaticaly.

            You mean the correct account won't just show up automatically based on the website or app that you're using? Because if so, that's not the case for me.