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

Re: Custom Elements: insert/remove callbacks

From: Anne van Kesteren <annevk@annevk.nl>
Date: Wed, 6 May 2015 17:25:54 +0200
Message-ID: <CADnb78j1_niSrSq=OakKhscx2z_oK6TLGi4L63HSfuSAM8uAxg@mail.gmail.com>
To: Dimitri Glazkov <dglazkov@google.com>
Cc: WebApps WG <public-webapps@w3.org>
On Wed, May 6, 2015 at 4:34 PM, Dimitri Glazkov <dglazkov@google.com> wrote:
> 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.

I see. We know from HTML that a change of parent element might be
significant, e.g. with <picture> or the <details>  element. I'm
inclined to make a proposal here that we change these callbacks to be
the primitives the DOM offers rather than these higher-level
callbacks.


-- 
https://annevankesteren.nl/
Received on Wednesday, 6 May 2015 15:26:17 UTC

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