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: Tue, 13 Jan 2015 16:05:11 +0100
Message-ID: <CADnb78ht-FCgkYePQVYoJYVYBjAbXeGYAJZD--yLvsFz9pAZ-g@mail.gmail.com>
To: Ryosuke Niwa <rniwa@apple.com>
Cc: Webapps WG <public-webapps@w3.org>
On Tue, Jan 13, 2015 at 6:15 AM, Ryosuke Niwa <rniwa@apple.com> wrote:
> Have you settled the question of what happens to a custom element that's adopted into another document?

More or less...

> As far as I tested, WebKit and Blink keep the old __proto__ while Gecko changes it to the adopted document's prototype.  There is a bug in DOM component about this:
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=20567

So, the basic agreement as I understand it:

* Normal elements change their prototype during adoption
* Custom elements get a callback to be able to implement the same thing

Now the outstanding questions:

* Should normal elements change their prototype at the same point in
time custom elements have the opportunity to change theirs, or should
it happen synchronously?
* Does it make sense that when subclassing a normal element this
automatic prototype changing aspect gets lost?

Received on Tuesday, 13 January 2015 15:05:38 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:43 UTC