- From: Emil Lundberg via GitHub <sysbot+gh@w3.org>
- Date: Thu, 02 Nov 2017 10:20:29 +0000
- To: public-webauthn@w3.org
The current prose is equivalent to making `PublicKeyCredentialEntity.name`, `PublicKeyCredentialUserEntity.id` and `PublicKeyCredentialUserEntity.displayName` required in the IDL. However, it looks like it's been deliberately decided to specify this in text instead of IDL. In #538 @AngeloKai says >The issue was brought up in past discussions around CredMan. [...] I believe the required keyword on IDL is omitted due to the need to integrate with CredMan. @mikewest probably has better memory about this. The argument is that it is ok for the keyword to be omitted as long as a DOM Exception error would be thrown. >[...] >We decided to remove the required keyword and let JS throw the TypeError so that the inheritance would be clearer. I don't understand why having them not required is needed for integration with CredMan, since all these types are specific to WebAuthn and we can have required members in other dictionaries. I'm in favor of making the members required in IDL; but I'm also in favor of closing this with no action if it would break CredMan integration, and since nothing seems to have changed to make the decision in #538 out of date. @AngeloKai @mikewest Any objections to making the required members required in IDL? -- GitHub Notification of comment by emlun Please view or discuss this issue at https://github.com/w3c/webauthn/issues/587#issuecomment-341377135 using your GitHub account
Received on Thursday, 2 November 2017 10:20:31 UTC