Re: [webauthn] Allow Conditional Mediation without autofill (#2144)

_Thanks for bringing my question over to here @kenrb. Here's the full comment I left over in #2435:_

Is `mediation: "conditional"` _really_ necessary to trigger the ambient UI experience?

The reason I ask is, one of the motivations listed in the updated explainer is that "Conditional UI is not useable because there is not a sign-in form on the page." It doesn't make sense to me on pages that don't have a login form why the RP would call `.get()` with `mediation: "conditional"` when the page would otherwise not be in a state to do so.

Could not the logic for triggering ambient UI simply be the presence of `uiMode: "passive"`?

```js
const cred = await navigator.credentials.get({
  // mediation: 'conditional',  // <-- Omitted
  uiMode: 'passive',  // <-- This alone triggers ambient UI
  publicKey: {
    challenge: ...,
    rpId: 'example.com',
    allowCredentials: {...},
    display: 'ambient',
  },
  password: true,
});
```

Then, on pages that **do** feature a login form, the RP can **combine** `uiMode: "passive"` with `mediation: "conditional"` to get the typical browser autofill on the form `<input>`s, while also triggering ambient UI at the same time.

-- 
GitHub Notification of comment by MasterKale
Please view or discuss this issue at https://github.com/w3c/webauthn/issues/2144#issuecomment-4791430906 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 24 June 2026 16:22:29 UTC