- From: Travis Leithead <notifications@github.com>
- Date: Wed, 02 Mar 2016 14:29:50 -0800
- To: w3c/webcomponents <webcomponents@noreply.github.com>
Received on Wednesday, 2 March 2016 22:30:20 UTC
This is a problem for both instantiation via the parser, and for upgrade, right? I think I land on the side of not instantiating merely because the expectation of template content in the first place is to deep-clone it for later use. The cloning process will [maybe?] instantiate a new custom element anyway--why do the work twice? --- Reply to this email directly or view it on GitHub: https://github.com/w3c/webcomponents/issues/406#issuecomment-191465100
Received on Wednesday, 2 March 2016 22:30:20 UTC