Re: [w3c/webcomponents] Presence of disconnectedCallback can expedite an invocation of connectedCallback (#760)

Use-case which needs a note/warning in spec or at least MDN https://github.com/w3c/webcomponents/issues/760
```js
class ParentElement extends HTMLElement {
    connectedCallback() {
        const child = this.childNodes[0];

        log('Child removal begin');
        this.removeChild(child);
        log('Child removal end');
    }
}
customElements.define('parent-element', ParentElement);

class Child1 extends HTMLElement {
    connectedCallback() {
        log('Child connectedCallback isConnected=' + this.isConnected.toString());
    }

}
customElements.define('child-1', Child1);

const container = document.createElement('div');
container.innerHTML = '<parent-element><child-1></child-1></parent-element>';
customElements.upgrade(container);
document.body.appendChild(container); 
// Child connectedCallback isConnected=false
```

-- 
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/760#issuecomment-433160831