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

@rniwa If we don't add anything to the spec, then as @wiredearp suggested, many authors will need to similarly wrap their callback logic in `document ready` handlers, which is exactly what I've done in my above examples.

Many people are going to do something like this, using jQuery:

```js
connectedCallback() {
  $(document).ready(() => {
    doSomethingWithUpgradedChildren(this.children)
  })
}
```

> FWIW, it could be being blocked by the network!

I'd rather wait for the closing tag of an element, even if that means waiting for the network, and therefore for inner element constructors and connectedCallbacks to _**ALWAYS**_ fire in the same order.

This will simply make programs predictable and reliable.

Just imagine the trouble React and Vue would cause if they ran life cycle methods in arbitrary ordering depending on this or that. It'd be a tsunami of issues flooding GitHub.

Most people these days are not blocked by network on fetching DOM. At least, it's not a significant problem on any sites I ever visit, or the time it takes is always fast enough that I don't notice any problems.

-- 
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-335047016