Re: [w3c/webcomponents] Add list of major open design questions to HTML Modules proposal doc (#801)

matthewp commented on this pull request.



> @@ -124,6 +124,16 @@ This example demonstrates how the above custom element definition can be consume
 
 [main.html](demo/main.html)
 
+## Major open design questions
+
+The following list is **not** comprehensive of all open issues; the intent here is to highlight questions that could have a significant impact on the shape of the final design depending on the way they are decided.
+
+- Should HTML Modules use a new MIME type, or the existing `text/html`? [[1](https://github.com/w3c/webcomponents/issues/742)]
+- How should HTML modules interact with CSP?  In particular, should their inline scripts be allowed to run even without an `unsafe-inline` directive? [[1](https://github.com/w3c/webappsec/issues/544)], [[2](https://discourse.wicg.io/t/proposal-html-modules/3309/2)]
+- Should non-`type="module"` scripts in an HTML module yield an error or be implicitly interpreted as module scripts? [[1](https://github.com/w3c/webcomponents/issues/798)]
+- Should there be a declarative way to consume HTML modules?

This is an interesting issue that I didn't know about because I don't follow MSEdgeExplainers (I will now!). Is the intent to open an issue here about that subject or is your team debating it amongst yourselves first?

-- 
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/pull/801#pullrequestreview-211380571