W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2015

Re: Custom element lifecycle callbacks

From: Boris Zbarsky <bzbarsky@mit.edu>
Date: Fri, 09 Jan 2015 10:11:23 -0500
Message-ID: <54AFEF9B.9080805@mit.edu>
To: Anne van Kesteren <annevk@annevk.nl>
CC: WebApps WG <public-webapps@w3.org>
On 1/9/15 9:33 AM, Anne van Kesteren wrote:
> On Fri, Jan 9, 2015 at 3:09 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote:
>> In any case, the fact that we're even _having_ this discussion and that it
>> needs careful reading of the HTML spec is my point.
> It does seem however we could define this in a way that is safe.

If by "this" you mean cloning of file inputs, then obviously yes.  I 
never implied otherwise, as far as I can tell.

If by "this" you mean "a change from the current behavior to delayed 
cloning steps, without auditing all the cloning steps to make sure we 
don't end up in weird inconsistent states", then I don't think so.  You 
really do have to carefully audit all the cloning steps in the spec, as 
well as any future cloning steps.

Received on Friday, 9 January 2015 15:11:55 UTC

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