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