Browser Support

The WebAuthn spec is one thing; what each browser does with it is another. This series covers the behaviour that differs in practice - Safari's user activation requirement, Chrome's conditional UI on older Windows, Brave's handling of passkeys, and what user-agent client hints can and cannot tell you about a visitor's capabilities.

Each article stands on its own - start wherever your problem is.

1. Chrome Conditional UI: isConditional MediationAvailable() Returns True on Windows 10

   Recently, the JavaScript API method isConditionalMediationAvailable() returns true for Windows 10 devices, which are not Conditional UI ready. Read why.

   WebAuthn Know-How·Mar 2024

2. Client Hints & User-Agents in Chrome, Safari & Firefox

   Learn about User-Agent & Client Hints API support in Chrome, Safari & Firefox and how we use them for passkeys & device detection in JavaScript components.

   Engineering·Jul 2024

3. Passkeys in Brave Browser (2026): What Works and Breaks

   Brave mostly follows Chromium for passkeys, but Android, Windows Hello and password-manager conflicts still create real friction.

   WebAuthn Know-How·Apr 2026

4. Safari WebAuthn User Gesture Requirements Not Detected

   Avoid Safari passkey errors: Learn how to handle user gesture requirements for WebAuthn on iOS and build seamless, cross-version passkey login flows.

   WebAuthn Know-How·May 2024