Kevin Smith wrote:
>
>
>         Is a new attribute necessary? What about using @type?
>
>
>     Old browsers will ignore unknown types, losing the two-way
>     fallback option.
>
>
> Two-way fallback?  Why is that important?  Since modules are 
> implicitly strict, there is little intersection between scripts and 
> modules.

One can write strict code that runs fine in old browsers!

Why do we want inline module-bodied elements in HTML? That's the topic 
here. There is no issue for out-of-line module-bodied elements, AFAICT. 
Once you focus on inline bodies, you face harsh adoption barriers 
without enabling works-in-old-and-new coding.

/be

Kevin Smith wrote:

> Two-way fallback?  Why is that important?  Since modules are 
> implicitly strict, there is little intersection between scripts and 
> modules.

One can write strict code that runs fine in old browsers!

Why do we want inline module-bodied elements in HTML? That's the topic 
here. There is no issue for out-of-line module-bodied elements, AFAICT. 
Once you focus on inline bodies, you face harsh adoption barriers 
without enabling works-in-old-and-new coding.