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

Re: Adopting a Custom Element into Another Document

From: Anne van Kesteren <annevk@annevk.nl>
Date: Wed, 14 Jan 2015 09:42:34 +0100
Message-ID: <CADnb78g5PdVFVH2GP9BrZXr51=R7W6KQzNPgygxDx6yGuFFCug@mail.gmail.com>
To: Ryosuke Niwa <rniwa@apple.com>
Cc: Webapps WG <public-webapps@w3.org>, Boris Zbarsky <bzbarsky@mit.edu>
On Tue, Jan 13, 2015 at 8:36 PM, Ryosuke Niwa <rniwa@apple.com> wrote:
> I'm not sure I understand what you mean by that.  The name of the new class MyElementB isn't important.
>
> Do you agree that the author has to create a new class in B if there is no definition of MyElement there?

Yes.


> But how do we even determine whether MyElement's defined in B?

Who is we?


> And if did, how do we get the class's prototype?

In the proposed setup the developer just gets an adopted callback and
can then do whatever they want. Either cleaning up the giant memory
leak or leaving it in.


-- 
https://annevankesteren.nl/
Received on Wednesday, 14 January 2015 08:42:58 UTC

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