![]() ![]() the extension should not plough into the biometric dialogue until the user actually clicks the "unlock with biometrics" option. That's probably worth raising as a separate bug in its own right (if there isn't already one) - ie. The only workaround seems to be to hard-close the desktop client altogether, so that the biometric attempt never happens at all, and only then will the extension allow "local" login (master password and/or PIN). ![]() Is this a variation on part of the original problem, where in practice with a mismatched extension ( #6156, #6185) it's actually very difficult to unlock the extension at all - the biometric unlock dialogue is triggered (and then fails, due to the API breakage) without giving the user a chance to unlock in any other way. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress. I understand that work is tracked outside of Github.Windows 11 22H2, Windows 10 22H2 Web Browserįirefox Extension v2023.8.3 Issue Tracking Info ![]() ![]() There are may one or two star reviews from last week on Firefox Addons with login issues using biometrics too. I haven't any issues last week so it is maybe regression with new version 2023.8.3 (from Addons website: Last updated: 7 days ago (7. Screenshots or VideosĮxtension is not working on my two desktop systems. Actual ResultĮnter key is ignored, I can't submit existing PIN. I can unlock vault using PIN, I can enable Unlock by PIN option. "Enter PIN" field is not responding to Enter key, OK button is not working too Expected Result
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |