- From: Addy Osmani <notifications@github.com>
- Date: Tue, 20 Jun 2017 09:00:04 -0700
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 20 June 2017 16:00:53 UTC
Thanks for getting a public discussion going, @justinfagnani! I see HTML Modules as being a good container format for achieving generic subresource dependency specification. They solve my need for platform-level colocated `<template>`, `<style>` and `<script>`/Module in a similar style to what I would get with something like Vue's .vue files or Polymer's existing HTML Imports. One question I would ask is what it is about HTML Modules that makes them specific to Web Components? If a third-party decides to just use HTML + CSS + JS in this container format, that should just work too right? I'm also interested in where we see HTML Modules fitting with respect to the semi-related Web Packaging efforts. -- 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-309805753
Received on Tuesday, 20 June 2017 16:00:53 UTC