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

Re: Custom Elements: Upgrade et al

From: Anne van Kesteren <annevk@annevk.nl>
Date: Wed, 6 May 2015 17:37:34 +0200
Message-ID: <CADnb78j39BEc51KxkvjmRktffk5Xc9=hLhB9rcRgJENU6mVRqQ@mail.gmail.com>
To: Dimitri Glazkov <dglazkov@google.com>
Cc: Domenic Denicola <d@domenic.me>, WebApps WG <public-webapps@w3.org>
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:


<canvas> does no such thing.

Received on Wednesday, 6 May 2015 15:38:07 UTC

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