Module doesn't work with legacy browsers

[marcoscaceres]

For legacy reasons, I'm not sure we can add a new tag to the head? Doing so you end up with a dom that looks like this (based on your example in the explainer):

And you end up with the script being displayed in the page, also... which kinda sucks.

Maybe you want a link rel="module" instead and keep using <script defer> for inline modules?

[dherman]

The stopgap solution should be a custom MIME type like <script type="application/javascript+module">. There's another evolutionary issue which is that legacy browsers won't treat it as implicitly CDATA. All of these issues are solved by allowing people to use the special script type as an interim syntax, and longer-term, once enough browsers support <module>, people can start using that.

But it's crucial to have the end state be a programming model where the syntax is as convenient as <script> is today (note that link rel="module" fails this explicit constraint listed in the requirements document).

I'll update the documents to reflect this before closing the issue.

[marcoscaceres]

Thanks for the clarification.