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

@emlun Thank you!  That does look like the right thing now, and it's doing the "is missing" check I was kinda looking for.

But I think  you're right about the name mismatch being a problem.  @equalsJeffH how could it not  cause  issues?  The algorithm checks whether the dictionary has a "public-key" member, which it never does if the dictionary member is called "publicKey".

-- 
GitHub Notification of comment by bzbarsky
Please view or discuss this issue at https://github.com/w3c/webauthn/issues/750#issuecomment-403622902 using your GitHub account

Received on Monday, 9 July 2018 21:15:32 UTC