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

[Bug 29438] JSON.stringify as invoked by wrapKey can have side-effects depending on what you pass it

From: <bugzilla@jessica.w3.org>
Date: Tue, 09 Feb 2016 20:16:34 +0000
To: public-webcrypto@w3.org
Message-ID: <bug-29438-7213-yDjp16iiVn@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29438

--- Comment #3 from Harry Halpin <hhalpin@w3.org> ---
(In reply to Ryan Sleevi from comment #1)
> Assigning to Mark; Adding Harry and Virginie on a process point if Bugzilla
> or GitHub should be used and what should be done to the old links (in the TR
> directory)

My guess is that we should just migrate everything to Github. We could use this
as a good exercise in checking to make sure all the bugs that are still open
have a closed state or at least are re-activated as we are going to make a
another push on the spec. 

If someone (hint hint) wants to do that, that, this would be grand. Otherwise,
I can do it over the weekend.


> 
> Yes, the intent is no observable effects, and I agree, this is a defect. Do
> you have suggestions on how to make that unambiguous?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Tuesday, 9 February 2016 20:16:38 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 9 February 2016 20:16:38 UTC