W3C home > Mailing lists > Public > public-webcrypto@w3.org > February 2016

[Bug 29437] Parsing a JWK can have side-effects if not done very carefully

From: <bugzilla@jessica.w3.org>
Date: Mon, 08 Feb 2016 23:13:35 +0000
To: public-webcrypto@w3.org
Message-ID: <bug-29437-7213-q8hj4AxYcC@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29437

Ryan Sleevi <sleevi@google.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|sleevi@google.com           |watsonm@netflix.com

--- Comment #1 from Ryan Sleevi <sleevi@google.com> ---
Latest ED is https://github.com/w3c/webcrypto

The intent was without depending on any external state (including the page
global), hence the distinction of "internal function" trying to clarify, but
apparently, poorly. Any suggestions for how to clarify that global? (The best
answer I got from the Chrome folks was just hand-wave and say "internal
function for everything")

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Monday, 8 February 2016 23:13:37 UTC

This archive was generated by hypermail 2.3.1 : Monday, 8 February 2016 23:13:37 UTC