I am using FireFox for Android (and even tried many of its variants like Fennec). Unfortunately, the Auto Fill feature never works from the first time if the vault is locked.
Steps that fail:
Open a website with a form.
Click the empty field and choose AutoFill with Bitwarden.
Put in the master password to unlock the vault.
At this point you expect BitWarden to unlock the vault AND fill the form, however, when I do this, it doesn’t fill the fields at all.
Steps that work:
Open a website with a form.
Click the empty field and choose AutoFill with Bitwarden.
Put in the master password to unlock the vault.
Refresh the page again.
Click the empty field and choose AutoFill with Bitwarden (which has already been unlocked in the previous step).
Now only it is able to fill the fields.
Would you please check this bug and fix it? It has been ongoing for several months now.
Same problem here. Works fine with Chrome, but on FF only as you described.
Is this a Bitwarden or FF issue?
Phone: OnePlus 7, Android: 11, FF: 88.1.4.
I was reading a lot about this issue and wanted to provide a very quick workaround that helped me.
let style = window.getComputedStyle(document.getElementById('email'))
if (style && style.backgroundColor !== inputBackgroundNormalState) {
this.inputAutofilledByBrowser = true
}
where inputBackgroundNormalState for my template is ‘rgb(255, 255, 255)’.
So basically when browsers apply autocomplete they tend to indicate that the input is autofilled by applying a different (annoying) yellow color on the input.
I am still facing this issue on Firefox Android. I am not sure if this is a problem with Bitwarden or Firefox. The Bitwarden autofill popup does appear but it does not autofill.
Yeah never got this resolved. It’s sad that Bitwarden team is ignoring such bug in an important browser like FireFox. Is there anyway we can draw their attention to that problem?
Do you think you can support us by moving this thread to another category that can be seen by the team as a bug report? It seems to be a bug that a lot of people are complaining about.
@tgreer I’m also finding that it isn’t working on Chrome on Windows 10 either for sites where it used to work before - all since the latest update. Is that a known issue too? (currently on 1.56.5)