nomodule attribute on script tag

[robbie-mac]

Reading the spec in its current form, it states that adding the nomodule attribute to the script tag will prevent execution of said script.

What would be the barriers to changing the spec to prevent requesting the resource, as in ignoring the tag completely, and not just preventing execution of the script?

If I understand correctly, this is to ease migration to an es2015 modules, and maybe an HTTP/2 way of thinking. During the trasnsition, if we are following best practices and bundling our code, we end up with a huge (potentially) download only to have it not executed, thus wasting the bandwidth.

Or am I missing something?

[domenic]

If you read the actual processing model, you'll see that the resource is indeed not requested. You're probably reading an imprecise non-normative description somewhere.

[robbie-mac]

@domenic Thanks for the quick reply. Ill file a bug with Mozilla. Firefox (Developer edition) with modules enabled requests the resource, but does not execute the script.