- From: Boris Zbarsky via GitHub <sysbot+gh@w3.org>
- Date: Tue, 09 Jan 2018 07:18:16 +0000
- To: public-webauthn@w3.org
OK, so... The thing in the `AuthenicationExtensions` is an `any`. That means that it can be any JS value.
1) What defines how arbitrary JS values are transformed into "A single JSON string prompt"? If I pass in `{ toString: function() { return 'x'; }, valueOf: function() { return 'y'; } }` as the value in the `AuthenticationExtensions`, then what will the resulting "JSON string prompt" be and why?
2) The concept of "JSON string" is not linked here. Does it mean https://tools.ietf.org/html/rfc8259#section-7 or something else? Note that encoding of a given Unicode string into the format described here is not unique. Also, does the "JSON string" form include the opening and closing `"` in this case?
3) What happens to unpaired surrogates? They're not "Unicode characters" per the Unicode definitions, so it's not clear to me that their representation in a "JSON string" as defined in https://tools.ietf.org/html/rfc8259#section-7 is actually defined.
Basically, none of my questions from https://github.com/w3c/webauthn/issues/626#issuecomment-337118928 seem to be answered in even this simplest case, unless I'm really missing something.
--
GitHub Notification of comment by bzbarsky
Please view or discuss this issue at https://github.com/w3c/webauthn/issues/626#issuecomment-356200188 using your GitHub account
Received on Tuesday, 9 January 2018 07:18:19 UTC