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

On Fri, Mar 22, 2013 at 8:42 AM, Anne van Kesteren <> wrote:
> On Fri, Mar 22, 2013 at 6:27 AM, Hajime Morrita <> 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?


Received on Friday, 22 March 2013 16:29:18 UTC