- From: Joe Pea <notifications@github.com>
- Date: Wed, 30 Jan 2019 21:30:47 -0800
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 31 January 2019 05:31:08 UTC
@rniwa It keeps getting more complicated: now if we create an instance with `new`, f.e. `new TestElement`, then add children to it but avoid calling `childConnectedCallback` because `isConnected` is false, then we have to somehow ensure that when the element is connected we'll fire `childConnectedCallback` for its children. Now we're back at square one again, trying to do the same thing we couldn't do before without a macrotask! So if we want to fire `childConnectedCallback` initially for the element's children in `connectedCallback` because `isConnected` being `false` prevented us from firing it before connecting, then we have no choice but to use `setTimeout`! Is there another way? -- 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/787#issuecomment-459221098
Received on Thursday, 31 January 2019 05:31:08 UTC