Re: [webauthn] `CredentialRequestOptions` make otherwise valid values invalid in an undesirable way

In Chromium, we have set the members of `CredentialCreationOptions` as nullable ([source]( Thus if a given member isn't present, it's null, and then everything works out.

That contrasts with [what's in Webauthn]( 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 using your GitHub account

Received on Wednesday, 3 October 2018 17:36:22 UTC