- From: Adam Powers via GitHub <sysbot+gh@w3.org>
- Date: Tue, 30 Jan 2018 06:43:51 +0000
- To: public-webauthn@w3.org
apowers313 has just created a new issue for https://github.com/w3c/webauthn: == Processing extensions as JSON == `AuthenticatorExtensions` are [defined as](https://www.w3.org/TR/2017/WD-webauthn-20171205/#typedefdef-authenticationextensions) an array of strings, presumably stringified JSON. Extensions talk about processing JavaScript object, such as the processing described in the [example extension](https://www.w3.org/TR/2017/WD-webauthn-20171205/#sctn-example-extension). No mention is ever made of parsing JSON into a JavaScript object, nor how a browser should behave if JSON parsing fails. For example see [step 12 of create processing](https://www.w3.org/TR/2017/WD-webauthn-20171205/#createCredential). Maybe add an extra step there that says: `The browser parses the extension from JSON to a JS object. If parsing fails, throw a TypeError.` And the same for [step 9 of get processing](https://www.w3.org/TR/2017/WD-webauthn-20171205/#getAssertion). Please view or discuss this issue at https://github.com/w3c/webauthn/issues/770 using your GitHub account
Received on Tuesday, 30 January 2018 06:43:59 UTC