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

Re: Custom Elements: Upgrade et al

From: Ryosuke Niwa <rniwa@apple.com>
Date: Wed, 06 May 2015 15:23:32 -0700
Cc: Dimitri Glazkov <dglazkov@google.com>, Domenic Denicola <d@domenic.me>, WebApps WG <public-webapps@w3.org>
Message-id: <F884361A-77F2-4C2B-AA38-9DE06B0215F0@apple.com>
To: Anne van Kesteren <annevk@annevk.nl>

> On May 6, 2015, at 8:37 AM, Anne van Kesteren <annevk@annevk.nl> wrote:
> On Wed, May 6, 2015 at 4:59 PM, Dimitri Glazkov <dglazkov@google.com> wrote:
>> On Wed, May 6, 2015 at 7:50 AM, Domenic Denicola <d@domenic.me> wrote:
>>> Can you explain how you envision cloning to work a bit more? Somehow there
>>> will be instances of these elements which are not created by their
>>> constructors?
>> Also, how is it in any way similar to  how <canvas> or <input> work? I am
>> pretty sure both of those are constructed during cloning.
> The proposal would be to change that. You can construct an instance.
> And you can create a second instance either by cloning the first or
> constructing a new one.
> The difference between <canvas> and <input> is that for <input> we
> also clone private state using this hook:
>  https://dom.spec.whatwg.org/#concept-node-clone-ext
> <canvas> does no such thing.

Are you suggesting that cloning my-button will create a new instance of my-button by invoking its constructor?

- R. Niwa
Received on Wednesday, 6 May 2015 22:24:03 UTC

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