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

Re: [webcomponents]: Invocation order of custom element readyCallback

From: Hajime Morrita <morrita@google.com>
Date: Sun, 24 Mar 2013 10:06:10 +0900
Message-ID: <CALzNm5rGoiyNWS4-PT0b8GmZpodD6Wa-77EXMGHMuvQxRNedow@mail.gmail.com>
To: Dimitri Glazkov <dglazkov@chromium.org>
Cc: Scott Miles <sjmiles@google.com>, Anne van Kesteren <annevk@annevk.nl>, public-webapps <public-webapps@w3.org>
On Sat, Mar 23, 2013 at 3:25 AM, Dimitri Glazkov <dglazkov@chromium.org>wrote:

> On Fri, Mar 22, 2013 at 9:35 AM, Scott Miles <sjmiles@google.com> wrote:
> > In our work, we adopt a composition rule that a node knows about it's own
> > children and can have expectations of them, but can make no assumptions
> > about it's parent or siblings. As a coding model we've found it to be
> > deterministic enough to build sane constructions. For example, you can
> use
> > methods/properties on your children, but should only fire events upward.
>

Yup. My assumption was that for a custom element, its children matter more
than its parent or siblings.

>
> > Therefore, our polyfills have an invariant that custom elements are
> prepared
> > bottom-up (i.e. my children are all upgraded before I am).
>
> Intuitively, I agree with Scott. Which means that the callback queue
> is LIFO, right?
>

Ah right. This sounds simple enough to be explained... and to be
implemented :-)


> :DG<
>



-- 
morrita
Received on Sunday, 24 March 2013 01:06:38 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:58 GMT