- From: Joe Pea <notifications@github.com>
- Date: Tue, 19 Mar 2019 11:48:42 -0700
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 19 March 2019 18:49:04 UTC
> Just as if you made a subtree then append it via appendChild. It's not quite the same as that because in that case I can make my elements with `new ` and connect them together while they are custom elements (didn't need to be upgraded). I can detect this case (using `new `) fine, and can work with children the way I want. And it also isn't the same initial-payload parser. Here's the issue, I made two fiddles showing the difference between initial-payload parser, and fragment parser: - this first one shows your technique from https://github.com/w3c/webcomponents/issues/787#issuecomment-458456606 works in initial parsing: https://jsfiddle.net/trusktr/psw530mf/1/ - and here's the same fiddle modified to use `insertAdjacentHTML`, and you'll see based on the output that MO does not fire initially: https://jsfiddle.net/trusktr/psw530mf/2/ Seems like I need to detect the difference between the two, and in the second case I need to manually trigger child-handling logic. -- 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-474521572
Received on Tuesday, 19 March 2019 18:49:04 UTC