- From: Adam Langley via GitHub <sysbot+gh@w3.org>
- Date: Fri, 23 Feb 2018 00:41:05 +0000
- To: public-webauthn@w3.org
To summarise what I've managed to get from emailing people who do know WebIDL: - Indeed, we cannot have an interface attribute with a dictionary value for unknown reasons. - We can define `AuthenticationExtensionsClientOutputs` as a series of `partial interface` chunks, one for each extension, and with the expectation that browsers will only implement a subset of the attributes. That, however, means that there'll probably be null-valued attributes for all the extensions that a client supports, even if those extensions weren't used in a given request. - We can also have a function returning a dictionary (i.e. what we had). I don't have a strong preference either way. I think the Javascript is a little cleaner if it's an interface, but not having null-valued attributes hanging around might swing it for some people. -- GitHub Notification of comment by agl Please view or discuss this issue at https://github.com/w3c/webauthn/pull/810#issuecomment-367871868 using your GitHub account
Received on Friday, 23 February 2018 00:42:48 UTC