W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2015

Re: Exposing structured clone as an API?

From: Jonas Sicking <jonas@sicking.cc>
Date: Mon, 27 Apr 2015 19:06:41 -0700
Message-ID: <CA+c2ei963TSOsYReEcx3KSXfP4o38o-Qg2aoNz35C6H77bpXyQ@mail.gmail.com>
To: Kyle Huey <me@kylehuey.com>
Cc: Boris Zbarsky <bzbarsky@mit.edu>, Web Applications Working Group WG <public-webapps@w3.org>
On Thu, Apr 23, 2015 at 6:31 PM, Kyle Huey <me@kylehuey.com> wrote:
> On Thu, Apr 23, 2015 at 6:06 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote:
>> On 4/23/15 6:34 PM, Elliott Sprehn wrote:
>>>
>>> Have you benchmarked this? I think you're better off just writing your
>>> own clone library.
>>
>>
>> That requires having a list of all objects browsers consider clonable and
>> having ways of cloning them all, right?  Maintaining such a library is
>> likely to be a somewhat demanding undertaking as new clonable objects are
>> added...
>>
>> -Boris
>>
>
> Today it's not demanding, it's not even possible.  e.g. how do you
> duplicate a FileList object?

We should just fix [1] and get rid of the FileList interface. Are
there more interfaces this applies to?

[1] https://www.w3.org/Bugs/Public/show_bug.cgi?id=23682

/ Jonas
Received on Tuesday, 28 April 2015 02:07:38 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:27:31 UTC