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

Re: Custom elements: synchronous constructors and cloning

From: Dimitri Glazkov <dglazkov@google.com>
Date: Tue, 24 Feb 2015 07:52:14 -0800
Message-ID: <CADh5Ky3bi5p1qJc8i2aWoQpwV+ZqtxjC0O0Sa_wiXJyXxW7wRg@mail.gmail.com>
To: Anne van Kesteren <annevk@annevk.nl>
Cc: Ryosuke Niwa <rniwa@apple.com>, Boris Zbarsky <bzbarsky@mit.edu>, WebApps WG <public-webapps@w3.org>, Yehuda Katz <wycats@gmail.com>
Filed https://www.w3.org/Bugs/Public/show_bug.cgi?id=28092 to add more data
to the informative content around the normative statement that makes this
happen.

On Tue, Feb 24, 2015 at 7:39 AM, Dimitri Glazkov <dglazkov@google.com>
wrote:

>
>
> On Tue, Feb 24, 2015 at 7:37 AM, Anne van Kesteren <annevk@annevk.nl>
> wrote:
>
>> On Tue, Feb 24, 2015 at 4:35 PM, Dimitri Glazkov <dglazkov@google.com>
>> wrote:
>> > Wait, what do you mean by "that is what custom elements provide for
>> today.."
>> >
>> > The entire pattern of template-stamping depends on the fact that custom
>> > elements aren't broken when cloning/importing.
>>
>> There's no hook for cloning, is there? Or is the created callback
>> supposed to be invoked? (If it is, that's missing from the
>> specification.)
>>
>
> There's no special hook for cloning, no. But the created callback is
> definitely invoked when cloning. The spec simply says that it's queued
> whenever an element is created.
>
>
>>
>>
>> --
>> https://annevankesteren.nl/
>>
>
>
Received on Tuesday, 24 February 2015 15:52:46 UTC

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