- From: Russell Bicknell <notifications@github.com>
- Date: Wed, 28 Jun 2017 22:37:11 +0000 (UTC)
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 28 June 2017 22:37:43 UTC
> The number one problem I see with this is that this is going after multiple problems at once. While `import * from './template.html` as DocumentFragment` could be nice for JavaScript, at least in the context of Web Components it seems unnecessary. IMO, separation into multiple types of import behaviors enables a key benefit (for both web components and script in general). If we can avoid having to define the one true way to import HTML with `import * from './template.html';` then we can avoid the inert DocumentFragments vs. templates vs. HTML-Import-like debate. This wouldn't preclude something similar to HTML Imports from being defined later and we also wouldn't have to block the ability to import HTML from script, as a whole, on that definition (assuming something like fragments or templates would be simpler to spec). -- 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/645#issuecomment-311811652
Received on Wednesday, 28 June 2017 22:37:43 UTC