- From: Adam Langley via GitHub <sysbot+gh@w3.org>
- Date: Wed, 03 Oct 2018 17:36:15 +0000
- To: public-webauthn@w3.org
In Chromium, we have set the members of `CredentialCreationOptions` as nullable ([source](https://cs.chromium.org/chromium/src/third_party/blink/renderer/modules/credentialmanager/credential_creation_options.idl)). Thus if a given member isn't present, it's null, and then everything works out. That contrasts with [what's in Webauthn](https://w3c.github.io/webauthn/#credentialcreationoptions-extension). Perhaps Webauthn should allow these fields to be nullable so that the required members within each subtype's options aren't a problem? -- GitHub Notification of comment by agl Please view or discuss this issue at https://github.com/w3c/webauthn/issues/750#issuecomment-426727905 using your GitHub account
Received on Wednesday, 3 October 2018 17:36:22 UTC