Re: [webcomponents]: Invocation order of custom element readyCallback from Anne van Kesteren on 2013-03-22 (public-webapps@w3.org from January to March 2013)

From: Anne van Kesteren <annevk@annevk.nl>
Date: Fri, 22 Mar 2013 12:42:56 +0000
To: Hajime Morrita <morrita@google.com>
Cc: public-webapps <public-webapps@w3.org>
Message-ID: <CADnb78gdMNKj=ycEe5+vLmwNkGtpGPgx9Z3_0+N8k2LX3AryOg@mail.gmail.com>

On Fri, Mar 22, 2013 at 6:27 AM, Hajime Morrita <morrita@google.com> wrote:
> So what about (B): Call <x-child> first and <x-parent> second? This solves
> the "unreadified <x-child>" problem.

And you will have a parent that is not ready.

Or if you have

<fb-1/><fb-2/>

you'll either have a previousSibling or nextSibling, depending on
invocation order, that's not ready. Or am I missing something?

-- 
http://annevankesteren.nl/

Received on Friday, 22 March 2013 12:43:28 UTC