nomodule attribute is not respected on scripts with sources #4281
Comments
mgol
added a commit
to mgol/jquery
that referenced
this issue
Jan 17, 2019
PR jquery#3869 added support for `<script type="module">` & some support for the `nomodule` attribute but with no tests for `nomodule` and with the attribute only respected on inline scripts. This commit adds support for source-based scripts as well. It also adds tests for `nomodule`, including making sure legacy browsers execute such scripts as they'd natively do - that's the whole point of `nomodule` scripts, after all. Fixes jquerygh-4281 Ref jquerygh-3871 Ref jquerygh-3869
|
PR: #4282 |
mgol
added a commit
that referenced
this issue
Jan 21, 2019
PR #3869 added support for `<script type="module">` & some support for the `nomodule` attribute but with no tests for `nomodule` and with the attribute only respected on inline scripts. This commit adds support for source-based scripts as well. It also adds tests for `nomodule`, including making sure legacy browsers execute such scripts as they'd natively do - that's the whole point of `nomodule` scripts, after all. Fixes gh-4281 Closes gh-4282 Ref gh-3871 Ref gh-3869
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
PR #3869 added support for
<script type="module">& some support for thenomoduleattribute but with no tests fornomoduleand with the attribute only respected on inline scripts.Ref #3871
Link to test case
http://plnkr.co/edit/rZJmEFJIpPOHDMNJUdxz?p=preview
In modern browsers you should see
PASS, instead you'll seeFAIL: 2, indicating 2 out of 4 scripts get executed; those are the src-based scripts.The text was updated successfully, but these errors were encountered: