[w3c/webcomponents] Please revisit HTML Imports (#677)

I'm disappointed by the industry rejection of HTML Imports. IMHO the web has needed declarative HTML imports since HTML 1.0. The lack of it has been the reason why so many server-side templating languages have needed to exist, when their only reason for being has been that web pages can re-use all assets across pages (JS and CSS) except for other HTML partials.

I think one of the reasons for this rejection is that the use-cases for HTML imports have been so narrowly scoped to defining custom elements. But the reason to have HTML imports extends far, far beyond web components to the fundamentals of web page construction.

I think if HTML Imports could be redefined with a broader scope, it would be more obvious to vendors that ES6 JS Modules are not a sufficient replacement for the power of what HTML Imports can do.

-- 
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/677