- From: Matthew Miller via GitHub <sysbot+gh@w3.org>
- Date: Thu, 27 Jul 2023 16:14:55 +0000
- To: public-webauthn@w3.org
> Note that [`isConditionalMediationAvailable()`](https://w3c.github.io/webauthn/#dom-publickeycredential-isconditionalmediationavailable) is defined in the Credential Management spec, and WebAuthn only overrides it, so unlike `isPPAA()` we cannot delete `isConditionalMediationAvailable()` in favour of `getClientCapabilities()`. So again in the interest of de-duplication, I think we should keep the conditional mediation check separate. In response to this point, I don't want [a point I made earlier](https://github.com/w3c/webauthn/pull/1923#issuecomment-1652394315) to get glossed over: > ...The idea is future capabilities checks get added as enums to this, and maybe there are convenience methods added too that make an appropriate call to this method behind the scenes. I don't see `getCC()` replacing methods like `isPPAA()`. Rather I see there being value in a method `isPPAA()` essentially calling `getCC(['uvpaa', 'hybrid'])` behind the scenes. There's value in having "convenience methods" like `isPPAA()` to make it easier to use (and provide guidance on using a la https://passkeys.dev) WebAuthn, while still enabling RP's with more advanced use cases to drop down a level and call `getCC()` directly. -- GitHub Notification of comment by MasterKale Please view or discuss this issue at https://github.com/w3c/webauthn/pull/1923#issuecomment-1653932380 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 27 July 2023 16:14:57 UTC