- From: Mike Jones via GitHub <sysbot+gh@w3.org>
- Date: Tue, 09 Jan 2018 21:51:08 +0000
- To: public-webauthn@w3.org
Answering @bzbarsky 's questions: 1. Arbitrary JS values are not transformed into strings. You're expected to pass a string value for this extension. If you don't, it's an error. 2. I think that JSON string should be DOMstring 3. Unpaired surrogate processing would be the same as for an other Web interface using strings. There's nothing about this use case that requires custom Unicode processing. 4. Where were are the conversions from client extension inputs to authenticator extension inputs specified and where are the reverse conversions from authenticator extension outputs to client extension outputs defined? In the last paragraph of https://w3c.github.io/webauthn/#sctn-client-extension-processing . -- GitHub Notification of comment by selfissued Please view or discuss this issue at https://github.com/w3c/webauthn/issues/626#issuecomment-356425744 using your GitHub account
Received on Tuesday, 9 January 2018 21:51:10 UTC