Re: [w3c/webcomponents] HTML Modules (#645)

If we intended to make JavaScript mandatory then we would combine the
specs. As the HTML spec sits today JS and CSS support HTML, not the other
way around. We can make new specs that mix those concerns, but they would
not be HTML anymore. It would look like classic ASP or early PHP. It is
worth observing neither of these became specifications. Nor are either in
wide use today.

I am happy to support the use cases where components mix HTML/CSS/JS but
there are more use cases than this. As mentioned above, this is simply a
trend in some circles today. I do not support making this mandatory. HTML
Imports as it stands today requires JavaScript. As such i do not consider
HTML Imports finished.

If we finished the spec for HTML Imports, would we need HTML Modules at
all? A syntax similar to what Ashely proposes seems sufficient.

On Wed, Jun 21, 2017 at 12:07 Justin Fagnani <notifications@github.com>
wrote:

> @rniwa <https://github.com/rniwa> I wouldn't want to encode *only* what
> has become most popular today for two reasons:
>
>    1.
>
>    Because where we are now is largely a consequence of what capabilities
>    the platform has had. JavaScript developed popular user-land module systems
>    and loaders long before HTML Imports, and is now getting widespread native
>    modules before HTML. Given the lack of support HTML Imports has, Polymer
>    has had to carefully weigh it's options for working in browsers without
>    polyfills. If Polymer had decided to support a pure-JS distribution that
>    would have been be a pragmatic choice only and not an indication of what
>    we'd really like to use.
>    2.
>
>    The assertion (developers are putting HTML inside their JS, not JS
>    inside their HTML) might not be so absolute. Polymer and Vue are current
>    examples of libraries that support single-file HTML components with
>    scripts. There would be much more if it were a native capability.
>
> I'm not saying JS shouldn't also gain pre-loading and multi-module
> support, of course.
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/w3c/webcomponents/issues/645#issuecomment-310127748>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AGYGJ10U3td_PM_RGgRTbVQZGIfr5bY2ks5sGT_YgaJpZM4N_wrF>
> .
>


-- 
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-310206240