> On Jan 14, 2015, at 12:25 PM, Domenic Denicola <d...@domenic.me> wrote: > > From: Ryosuke Niwa [mailto:rn...@apple.com] > >> Let me restate the problem using an example. Suppose we're parsing >> <my-element></my-element><my-other-element></my-other-element>. >> >> Once the HTML is parsed, the DOM tree is constructed with two DOM elements. >> Now we call the constructors on those elements. Without loss of generality, >> let's assume we're doing this in the tree order. >> >> We call the constructor of my-element first. However, inside this >> constructor, you can access this.nextSibling after calling super(). What's >> nextSibling in this case? An uninitialized my-other-element. > > Thanks, that is very helpful. And I'd guess that with the current spec, it's > an uninitialized my-other-element in the sense that its createdCallback has > not been called, even though its constructor (which does nothing beside the > normal HTMLElement/HTMLUnknownElement stuff) has indeed been called.
Precisely. - R. Niwa
