W3C home > Mailing lists > Public > public-webrtc@w3.org > March 2015

Re: PSA: JSON.stringify has changed behavior wrt DOM objects in Chrome

From: Tim Panton new <thp@westhawk.co.uk>
Date: Wed, 18 Mar 2015 14:24:27 +0000
Cc: Adam Bergkvist <adam.bergkvist@ericsson.com>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-Id: <012ED757-02E1-485F-8CA3-414FA23DE16A@westhawk.co.uk>
To: Harald Alvestrand <harald@alvestrand.no>

> On 18 Mar 2015, at 13:47, Harald Alvestrand <harald@alvestrand.no> wrote:
> On 03/18/2015 11:57 AM, Adam Bergkvist wrote:
>> On 18/03/15 11:38, Harald Alvestrand wrote:
>>> It would surprise me if WEBRTC is the only area where people use
>>> Json.stringify on DOM objects, so I'm waiting to see what the West Coast
>>> folks say when they wake up.
>>> It's possible that the right solution is to modify Json.stringify() to
>>> work in harmony with the new definitions, in which case we don't need to
>>> do anything.
>> We use specific WebIDL serializers [1] on these objects that specifies
>> that all attributes should be included in the serialization so I think
>> it's covered in the spec.
> Thanks - I'm kicking this back to our WebRTC people to figure out if the appropriate solution is to implement the serializers in Chrome.
> That's what we have canaries forů.

Received on Wednesday, 18 March 2015 14:25:01 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:18:04 UTC