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: Fri, 8 May 2015 07:24:31 +0200
Message-ID: <CADnb78i7WSR++0GfKNxoS=hpJfHL74iHvV0H=EM-dEp7hjEwOw@mail.gmail.com>
To: Boris Zbarsky <bzbarsky@mit.edu>
Cc: WebApps WG <public-webapps@w3.org>
On Thu, May 7, 2015 at 10:14 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote:
> In Gecko, yes.  The set of hooks Gecko builtin elements have today is,
> effectively:
>
> 1)  This element used to not have a parent and now does.
> 2)  This element has an ancestor that used to not have a parent and now
>     does.
> 3)  This element used to have a a parent and now does not.
> 4)  This element has an ancestor that used to have a parent and
>     now does not.

So that is more granular than what Dominic said Chrome has. I wonder
why there's a difference. Normally at the low-level things are pretty
close (or have a difference like linked list vs array).


-- 
https://annevankesteren.nl/
Received on Friday, 8 May 2015 05:24:55 UTC

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