Biometrics: BW App opens Windows Hello fine for Fingerprint, but Chrome & Edge browser extensions both have a problem
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 2k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 397
Description
### Steps To Reproduce
I am aware that there have been a number of posts regarding Biometric issues over many months/years. Most answers seem to be along the lines of: 'there is no problem...'.
I post here hoping that someone with much more experience than I can help me solve the annoyance, below. Do I have a problem with my set-up, or is the issue more widespread?
When I use the BW app on my laptop to unlock my vault using Biometrics, the Windows Hello pop-up appears and accepts a finger scan on the reader directly, with no other user input, as one would expect.
However, when I use the browser extension both in Chrome and in Edge to unlock the vault, the Windows Hello pop-up appears, BUT it requires a mouse click on the pop-up itself before it will accept a fingerprint scan.
This is a pain, and inefficient. This behaviour is only a recent (weeks) development here.
If my laptop is powered on but asleep, black screen, a simple swipe on the fingerprint scanner wakes up the machine and unlocks Windows with no dramas, and with no additional user input.
### Expected Result
When I click the Bitwarden browser extension in Chrome and in Edge to unlock my vault, I expect Windows Hello pop-up to appear and accept a finger scan, with no additional actions.
### Actual Result
When invoked using browser extensions in Chrome or Edge, Windows Hello requires a mouse click on the pop-up before it will accept a fingerprint scan.
### Screenshots or Videos
My issue is related to the browser extensions for Chrome and Edge, not the BW app.
I will be extremely grateful for advice to solve my issue.
### Additional Context
If my laptop is powered up but asleep, a simple swipe on the fingerprint scanner wakes up the machine and unlocks Windows with no dramas; no addition user inputs are required.
### Operating System
Windows
### Operating System Version
Windows 10 Pro 22H2 OS Build 19045.6216
### Installation method
Other, Direct Download (from bitwarden.com)
### Build Version
Version 2025.7.0 SDK 'main (f2bc708)' Shell 36.4.0 Renderer 136.0.7103.149 Node 22.15.1 Architecture x64
### Issue Tracking Info
- [x] I understand that work is tracked outside of GitHub. 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.
Contributor guide
Research direction
Start with the browser-extension unlock flow in Chrome and Edge and compare it with the Bitwarden app's Windows Hello behavior. Reproduce on Windows 10 Pro 22H2 using the reported build, and consider the issue done when a fingerprint scan is accepted without clicking the Windows Hello pop-up.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authentication, frontend, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100