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

Re: Custom Elements: insert/remove callbacks

From: Dimitri Glazkov <dglazkov@google.com>
Date: Wed, 6 May 2015 07:34:20 -0700
Message-ID: <CADh5Ky2FaXrc3ha+ooMXKZ53kGZC3Krh5ZWO5ASr+H6oncEt7w@mail.gmail.com>
To: Anne van Kesteren <annevk@annevk.nl>
Cc: WebApps WG <public-webapps@w3.org>
On Wed, May 6, 2015 at 6:45 AM, Anne van Kesteren <annevk@annevk.nl> wrote:

> Open issues are kept track of here:
>
>   https://wiki.whatwg.org/wiki/Custom_Elements
>
> This has come up before, but it came up again at the Extensible Web
> Summit so raising hopefully for the last time.
>
> The DOM has insert/remove primitives for nodes. Custom Elements uses
> "insertion into a document" and "removal from a document" which are
> quite a bit different and higher level. Why should we have different
> primitives here?
>

This is https://www.w3.org/Bugs/Public/show_bug.cgi?id=24866.

The way I remember it, the argument went like this: the most common use
case for this callback is to react to element becoming part of the main
document (the rough approximation of a nebulous concept "am I useful on the
screen?"), and making these callbacks be invoked in other cases may just be
noise for devs.

:DG<
Received on Wednesday, 6 May 2015 14:34:48 UTC

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