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

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

From: Erik Arvidsson <arv@chromium.org>
Date: Fri, 22 Mar 2013 12:28:31 -0400
Message-ID: <CAJ8+GohkX960rAQDYnJbpWiFqu1HrNPeetdGYRsg6v6D-WtZHA@mail.gmail.com>
To: Anne van Kesteren <annevk@annevk.nl>
Cc: Hajime Morrita <morrita@google.com>, public-webapps <public-webapps@w3.org>
On Fri, Mar 22, 2013 at 8:42 AM, Anne van Kesteren <annevk@annevk.nl> wrote:
> 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?

Nope. You got it. No matter which order we spec there will always be a
way to observe custom elements that have not yet done their
createdCallback. The question is just which order is better?


--
erik
Received on Friday, 22 March 2013 16:29:18 GMT

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