- From: christopher luna <notifications@github.com>
- Date: Fri, 17 Jul 2015 23:42:08 -0700
- To: w3c/webcomponents <webcomponents@noreply.github.com>
Received on Saturday, 18 July 2015 06:42:37 UTC
One way to see it, is that `HTML Imports` work more similar to a node.js `require`; in the sense that the solicited content is like a module that is now available to be used and manipulated - but you need to actually write code that uses it! Instead, what you are proposing is more similar to a PHP `include`; the way it works is like if the line doing the `include` is just replaced by the raw content of the imported file. It falls out of spec, because `HTML Imports` was designed for the former scenario, (that is, having the content "in scope", ready to be manipulated by the coder), and not for inserting raw content. Is not that is undesirable creating a new tag, is just that `HTML Import` is not about including raw content, so doing that would be the work of a completely new, different spec. --- Reply to this email directly or view it on GitHub: https://github.com/w3c/webcomponents/issues/280#issuecomment-122503262
Received on Saturday, 18 July 2015 06:42:37 UTC