- From: Ryosuke Niwa <notifications@github.com>
- Date: Tue, 19 Mar 2019 13:43:11 -0700
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 19 March 2019 20:43:34 UTC
> > Just as if you made a subtree then append it via appendChild. > > It's not quite the same as manual use of `appendChild`, because in that case I can make my elements with `new ` and connect them together while they are custom elements. I can detect this case (using `new `) just fine. EDIT: Ah, it's similar to using `createElement`, `appendChild` to make the tree and then insert it into the doc, and finally defining the elements _after_ the fact. I'm just saying that the behavior of upgrading is identical to `appendChild`, not saying that what you do or what you need to do in response to innerHTML is the same. Invoking `document.createElement` would synchronously construct a custom element so it's not same at all. Anyway, I'm going to close this issue. This issue isn't really appropriate for standards discussion. There are no use cases presented, and there doesn't seem to be any API or spec change proposal. -- 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/789#issuecomment-474576593
Received on Tuesday, 19 March 2019 20:43:34 UTC