![]() ![]() Plus if this issue gets fixed it's easy to switch back. I just have Firefox in the background so I can send pages from my desktop to my phone. It's not quite as good as Firefox but it's good enough. Personally I gave up on this a few weeks ago and switched to Vivaldi. ![]() You can refresh the page which resets the autofill process, and sometimes by clicking back and forth between username, password, and other fields on the page you can trick firefox into restarting autofill, but its unreliable. Extensions are built for every major browser like Chrome, Safari, Firefox and Edge alongside more obscure. The change above then closes out the geckoview, whatever that actually means, and presumably reopens it when firefox is back in the foreground, but in the process whatever autofill sequence is supposed to happen gets interrupted, causing you to be in a state where bitwarden is now ready to log in but firefox is no longer asking it to. Bitwarden has superb platform support, too. The problem is that when you need to log into your vault the active app switches to bitwarden and android tells firefox its no longer in front. Is that the case even if your 1password vault is locked? Firefox works fine as long as you logged into and unlocked bitwarden before attempting to use your web browser. Seems it is a Bitwarden issue, as 1password works fine (they don't hide browser (no onStop() event in this case and no issue) ![]()
0 Comments
Leave a Reply. |