W3C home > Mailing lists > Public > public-webauthn@w3.org > March 2018

Re: [webauthn] JSON-serialized client data is wrong

From: =JeffH via GitHub <sysbot+gh@w3.org>
Date: Sat, 03 Mar 2018 00:12:26 +0000
To: public-webauthn@w3.org
Message-ID: <issue_comment.created-370094337-1520035945-sysbot+gh@w3.org>
Here's a n00b attempt at defining a "JSON stringify and UTF-8 encode to bytes" operation for the infra spec:
<p>To <dfn export>JSON stringify and UTF-8 encode to bytes</dfn> a given JavaScript value 
<var>value</var>, run these steps:

  <p>Let <var>jsonString</var> be the result of 
  <a abstract-op>Call</a>(<a>%JSONStringify%</a>, undefined, « <var>value</var> »).
  <p class=note>The conventions used in this step are those of the JavaScript specification.

 <li><p>Return the result of running <a>UTF-8 encode</a> on <var>jsonString</var>. [[!ENCODING]]

If I understand correctly, [\[ECMA-262\]](https://tc39.github.io/ecma262/) needs only a new row (after the `%JSONParse%` row) added to [Table 7 "well-known intrinsic objects"](https://tc39.github.io/ecma262/#table-7) like so (?):
%JSONStringify%      JSON.Stringify     The initial value of the 
                                        stringify data property of %JSON%

GitHub Notification of comment by equalsJeffH
Please view or discuss this issue at https://github.com/w3c/webauthn/issues/712#issuecomment-370094337 using your GitHub account
Received on Saturday, 3 March 2018 00:12:29 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 07:26:31 UTC