Re: [w3c/webcomponents] Custom Element definition ordering can cause difficult-to-find bugs. (#668)

Alright, so if I wait for the document to be ready, it seems I can work make my particular cases work:

```js
connectedCallback() {
 documentReady().then(() => {
  this.firstChild instanceof SomeCustomElement // TRUE
 })
}
```

but now I've introduced the ability for users of my elements to add/remove elements to/from DOM before document it ready, and who knows what bugs this could cause my elements. ¯\_(ツ)_/¯ 

I really think making any parsing atomic as far as CE is concerned would lead to programs that are likely to be more reliable.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/668#issuecomment-334989301

Received on Sunday, 8 October 2017 07:43:43 UTC