- From: Emil Lundberg via GitHub <sysbot+gh@w3.org>
- Date: Thu, 27 Jul 2023 12:53:22 +0000
- To: public-webauthn@w3.org
Some discussion points from the 2023-07-26 WG call: - (Fixed) `client-pin-entry` capability is too blunt; some external authenticators support internal UV, but the absence of this capability would make it seem like UV is not supported for those authenticators. - Given that [this together with `isUVPAA()` duplicates `isPPAA()`](https://github.com/w3c/webauthn/pull/1923#issuecomment-1650281617), I don't think this and `isPPAA()` should coexist. I prefer this `getClientCapabilities()` approach over `isPPAA()`, since the former is extensible and more explicit. If we merge this, I think we should revert #1901. (sorry Tim, no offense!) -- GitHub Notification of comment by emlun Please view or discuss this issue at https://github.com/w3c/webauthn/pull/1923#issuecomment-1653563362 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 12:53:23 UTC