Support in current browsers

Checked against the current browser versions recorded in MDN browser data 8.1.5.

BrowserMinimumOutcomeReason
Chrome155WorksEvery required mapped BCD feature is available without a recorded qualification.
Edge154WorksEvery required mapped BCD feature is available without a recorded qualification.
Firefox157WorksEvery required mapped BCD feature is available without a recorded qualification.
Safari27WorksEvery required mapped BCD feature is available without a recorded qualification.
Chrome for Android155WorksEvery required mapped BCD feature is available without a recorded qualification.
Firefox for Android157WorksEvery required mapped BCD feature is available without a recorded qualification.
Safari on iOS27WorksEvery required mapped BCD feature is available without a recorded qualification.
Android WebView155Works with limitsEvery required mapped feature is available, but BCD records one or more qualifications.
Samsung Internet30.0WorksEvery required mapped BCD feature is available without a recorded qualification.
The release trace

How support changed

Each segment groups recorded releases with the same result. Gaps between recorded versions are not filled in. This is support at each release, rather than the planner’s check of every release above a minimum.

Chrome

api.PublicKeyCredential.isConditionalMediationAvailable_static
  1. 1 – 107106 recorded releases
    Not supported
  2. 108 – 15548 recorded releases
    Works

Edge

api.PublicKeyCredential.isConditionalMediationAvailable_static
  1. 12 – 10735 recorded releases
    Not supported
  2. 108 – 15447 recorded releases
    Works

Firefox

api.PublicKeyCredential.isConditionalMediationAvailable_static
  1. 1 – 118121 recorded releases
    Not supported
  2. 119 – 15739 recorded releases
    Works

Safari

api.PublicKeyCredential.isConditionalMediationAvailable_static
  1. 1 – 15.632 recorded releases
    Not supported
  2. 16 – 2729 recorded releases
    Works

Chrome for Android

api.PublicKeyCredential.isConditionalMediationAvailable_static
  1. 18 – 10783 recorded releases
    Not supported
  2. 108 – 15548 recorded releases
    Works

Firefox for Android

api.PublicKeyCredential.isConditionalMediationAvailable_static
  1. 4 – 118102 recorded releases
    Not supported
  2. 119 – 15739 recorded releases
    Works

Safari on iOS

api.PublicKeyCredential.isConditionalMediationAvailable_static
  1. 1 – 15.629 recorded releases
    Not supported
  2. 16 – 2729 recorded releases
    Works

Android WebView

api.PublicKeyCredential.isConditionalMediationAvailable_static
  1. 1 – 130101 recorded releases
    Not supported
    • Partial implementation
    • Conditional mediation (autofill integration) is not supported; <code>isConditionalMediationAvailable()</code> always returns <code>false</code>.
  2. 131 – 15525 recorded releases
    Works with limits
    • Partial implementation
    • Conditional mediation (autofill integration) is not supported; <code>isConditionalMediationAvailable()</code> always returns <code>false</code>.

Samsung Internet

api.PublicKeyCredential.isConditionalMediationAvailable_static
  1. 1.0 – 20.042 recorded releases
    Not supported
  2. 21.0 – 30.010 recorded releases
    Works

BCD 8.1.5 · catalogue 2.3.0. Source corrections can change this trace without a new browser release.

What this feature can and cannot do

Helps protect against

  • Phishing-prone password dependence
  • Credential reuse

Does not guarantee

  • Account recovery weaknesses
  • Server-side authentication flaws
  • Every phishing and social-engineering path

What you need before using it

  • A complete WebAuthn flow
  • Secure account recovery
  • User-verification policy

Fallback to keep in place

Offer an explicit WebAuthn action and a carefully protected recovery path.