From f8f5f9993ad8572e57faec9156d37b3a0524d991 Mon Sep 17 00:00:00 2001
From: Dan Clark javascript
".
If module type is not "javascript
", "css
", or "json
", then asynchronously complete this
- algorithm with null, and return.
If the result of running the module type allowed steps given module + type and settings object is false, then asynchronously complete this algorithm + with null, and return.
Fetch a single module script given url, settings
object, "script
", options, settings object,
@@ -91437,8 +91437,8 @@ document.querySelector("button").addEventListener("click", bound);
Assert: module type is "javascript
", "css
", or "json
". Otherwise we would not have reached
+
Assert: the result of running the module type allowed steps given module + type and module map settings object is true. Otherwise we would not have reached this point because a failure would have been raised when inspecting moduleRequest.[[Assertions]] in create a JavaScript module script or @@ -91734,9 +91734,8 @@ document.querySelector("button").addEventListener("click", bound); data-x="">javascript".
If url is failure, or if module type is not "javascript
", "css
", or "json
",
- then:
If url is failure, or if the result of running the module type + allowed steps given module type and settings is false, then:
Let error be a new TypeError
exception.
If the CSSStyleSheet
interface is not exposed in setting's Realm, then return null.
Let script be a new module script that this algorithm will subsequently initialize.
Return script.
The module type allowed steps, given a string module type + and an environment settings object settings, are as follows:
+ +If module type is not "javascript
", "css
", or "json
", then return false.
If module type is "css
" and the
+ CSSStyleSheet
interface is not exposed in
+ setting's Realm, then
+ return false.
Return true.
To run a classic script given a classic script script