- From: Boris Zbarsky via GitHub <sysbot+gh@w3.org>
- Date: Wed, 25 Jul 2018 18:16:40 +0000
- To: public-webauthn@w3.org
How Gecko is dealing is as follows: 1) In Gecko right now, the `publicKey` member of `CredentialRequestOptions` is always present (and we throw if you try to call `CredentialsContainer.create` with an object without a `publicKey` property). 2) `CredentialsContainer.create` hardcodes the assumption that the only "relevant credential interface object" is `PublicKeyCredential`, since this is the only sort of credential we support and since we always have a `publicKey`. Needless to say, this looks nothing like the spec. I ran into this issue when trying to make our behavior more like the spec... -- GitHub Notification of comment by bzbarsky Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1004#issuecomment-407847855 using your GitHub account
Received on Wednesday, 25 July 2018 18:16:43 UTC