Re: [w3c/webcomponents] components v1 native implementation - inner components problem (#615)

I fix error, but problem left   http://jsbin.com/fopozupofa/1/edit?html,output  


>Вторник, 11 июля 2017, 6:14 +03:00 от Takayoshi Kochi <notifications@github.com>:
>
>I'm just seeing error message on Chrome with the jsbin demo,
>"error"
>"TypeError: Illegal constructor
>    at <anonymous>:9:11
>    at https://static.jsbin.com/js/prod/runner-4.0.4.min.js:1:13850
>    at https://static.jsbin.com/js/prod/runner-4.0.4.min.js:1:10792"
>...
>
>So I'm not completely sure the problem you are encountering, but as I understand  @annevk 's comment, the behavior you are seeing is working as expected.
>When HTML parser parses a custom element, it connects the parsed custom element after calling its constructor, but before connecting all the children which are not yet parsed. On the other hand, if all the custom elements are parsed but not upgraded (e.g. you put the custom elements in HTML before script that defines the custom element runs), when they are upgraded they can see their children, as they are already parsed and all connected (.innerHTML also parses, inserts, and then upgrades them, so you can see children).
>Closing this as working as expected.
>—
>You are receiving this because you were mentioned.
>Reply to this email directly,  view it on GitHub , or  mute the thread .



-- 
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/615#issuecomment-314318570