(In reply to Albert Scheiner [:alberts] from comment #2) > FYI, as an interim > > ### work-around 1 > 4. After Step #3 you tab the user or pass input field again > 5. Bitwarden focuses and you select the entry again > > Usually it gets filled in for me now > > ### work-around 2 > 4. After Step #3 while your vault is still unlocked you reload the page > 5. tab the user or pass input field again > > There should now be one or more additional items besides "Auto-fill with Bitwarden" you can select from of logins for this website. > > Hope that helps. A third work-around if you have Android 11 and a vault password: Bitwarden has support for password auto-fill via the keyboard. ### work-around 3 4. Do NOT perform step 3 ("Select the login entry from Bitwarden"), press back to return to web content instead after unlocking. 5. Observe that your keyboard has the in-lined password selector. 6. Select a password from there. > Calling releaseSession seems to be the right thing to do onStop. Is this a case GV needs to support or is there a way A-C can handle this? With my work-around, I imagine `releaseSession` was still called but auto-fill worked, so maybe it's something else related?
Bug 1693152 Comment 4 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Albert Scheiner [:alberts] from comment #2) > FYI, as an interim > > ### work-around 1 > 4. After Step #3 you tab the user or pass input field again > 5. Bitwarden focuses and you select the entry again > > Usually it gets filled in for me now > > ### work-around 2 > 4. After Step #3 while your vault is still unlocked you reload the page > 5. tab the user or pass input field again > > There should now be one or more additional items besides "Auto-fill with Bitwarden" you can select from of logins for this website. > > Hope that helps. A third work-around if you have Android 11 and a vault password: Bitwarden has support for password auto-fill via the keyboard. ### work-around 3 4. Do NOT perform step 3 ("Select the login entry from Bitwarden"), press back to return to web content instead after unlocking. 5. Observe that your keyboard has the in-lined password selector. 6. Select a password from there. (In reply to Christian Sadilek [:csadilek] from comment #1) > Calling releaseSession seems to be the right thing to do onStop. Is this a case GV needs to support or is there a way A-C can handle this? With my work-around, I imagine `releaseSession` was still called but auto-fill worked, so maybe it's something else related?
(In reply to Albert Scheiner [:alberts] from comment #2) > FYI, as an interim > > ### work-around 1 > 4. After Step #3 you tab the user or pass input field again > 5. Bitwarden focuses and you select the entry again > > Usually it gets filled in for me now > > ### work-around 2 > 4. After Step #3 while your vault is still unlocked you reload the page > 5. tab the user or pass input field again > > There should now be one or more additional items besides "Auto-fill with Bitwarden" you can select from of logins for this website. > > Hope that helps. A third work-around if you have Android 11 and a vault password: Bitwarden has support for password auto-fill via the keyboard. ### work-around 3 4. Do NOT perform step 3 ("Select the login entry from Bitwarden"), press back to return to web content instead after unlocking. 5. Observe that your keyboard has the in-lined password selector. 6. Select a password from there. --- (In reply to Christian Sadilek [:csadilek] from comment #1) > Calling releaseSession seems to be the right thing to do onStop. Is this a case GV needs to support or is there a way A-C can handle this? With my work-around, I imagine `releaseSession` was still called but auto-fill worked, so maybe it's something else related?