diff --git a/source b/source index 426157e0844..81701d8a63a 100644 --- a/source +++ b/source @@ -2755,6 +2755,7 @@ a.setAttribute('href', 'https://example.com/'); // change the content attribute
  • a promise resolved with
  • a promise rejected with
  • upon rejection
    • +
  • upon fulfillment
  • [LegacyFactoryFunction]
  • [LegacyLenientThis]
  • [LegacyNullToEmptyString]
    • @@ -2886,8 +2887,9 @@ a.setAttribute('href', 'https://example.com/'); // change the content attribute
  • The Script Record specification type
  • The Cyclic Module Record specification type
  • The Source Text Module Record specification type and its - Evaluate and - Link methods
    • + Evaluate, + Link and + LoadRequestedModules methods
  • The ArrayCreate abstract operation
  • The Call abstract operation
    • @@ -2901,6 +2903,7 @@ a.setAttribute('href', 'https://example.com/'); // change the content attribute
  • The DetachArrayBuffer abstract operation
  • The EnumerableOwnProperties abstract operation
  • The FinishDynamicImport abstract operation
    • +
  • The FinishLoadingImportedModule abstract operation
  • The OrdinaryFunctionCreate abstract operation
  • The Get abstract operation
  • The GetActiveScriptOrModule abstract operation
    • @@ -2911,10 +2914,9 @@ a.setAttribute('href', 'https://example.com/'); // change the content attribute
  • The HostEnqueuePromiseJob abstract operation
  • The HostEnsureCanAddPrivateElement abstract operation
  • The HostEnsureCanCompileStrings abstract operation
    • -
  • The HostImportModuleDynamically abstract operation
    • +
  • The HostLoadImportedModule abstract operation
  • The HostMakeJobCallback abstract operation
  • The HostPromiseRejectionTracker abstract operation
    • -
  • The HostResolveImportedModule abstract operation
  • The InitializeHostDefinedRealm abstract operation
  • The IsAccessorDescriptor abstract operation
  • The IsCallable abstract operation
    • @@ -95864,10 +95866,10 @@ document.querySelector("button").addEventListener("click", bound); sequence containing the response body. isTopLevel will be true for all classic script fetches, and for the initial fetch when fetching an external module script graph, fetching a module worker script graph, or fetching an import() module script graph, but false for the fetches - resulting from import statements encountered throughout the graph.

    + script graph">fetching an external module script graph or fetching a module worker script graph, but false for the fetches + resulting from import statements encountered throughout the graph or from + import() expressions.

    By default, not supplying a perform the fetch hook will cause the below algorithms to simply fetch @@ -96151,58 +96153,9 @@ document.querySelector("button").addEventListener("click", bound);

  • If result is null, run onComplete given null, and abort these steps.

    • -

  • Let visited set be « (url, "javascript") - ».

    • -

  • Fetch the descendants of and link result given settings object, "script", visited set, and onComplete.

    • - - - - -

    To fetch an import() module script graph given a moduleRequest, a - script, a settings object, some options, and an - onComplete algorithm, run these steps. onComplete must be an algorithm - accepting null (on failure) or a module script (on success).

    - -
      -

    1. Disallow further import maps given settings object.

      2. - -

    2. Let url be the result of resolving a - module specifier given script and moduleRequest.[[Specifier]], - catching any exceptions.

      3. - -

    3. If the previous step threw an exception, then run onComplete given null, and - return.

      4. - -

    4. Assert: moduleRequest.[[Assertions]] does not contain any - Record entry such that entry.[[Key]] is not "type", because we only asked for "type" assertions in - HostGetSupportedImportAssertions.

      5. - -

    5. Let moduleType be the result of running the module type from module - request steps given moduleRequest.

      6. - -

    6. If the result of running the module type allowed steps given - moduleType and settings object is false, then run onComplete - given null, and return.

      7. - -
    7. -

      Fetch a single module script given url, settings - object, "script", options, settings object, - "client", moduleRequest, true, and with the following steps - given result:

      - -
        -

      1. If result is null, run onComplete with null, and abort these - steps.

        2. - -

      2. Let visited set be « (url, moduleType) ».

        3. - -

      3. Fetch the descendants - of and link result given settings object, destination, - visited set, and onComplete.

        4. + data-x="">script", and onComplete.

    @@ -96225,18 +96178,11 @@ document.querySelector("button").addEventListener("click", bound);

  • Run onComplete given result.

  • -

    If result is not null, optionally perform the following steps:

    - -
      -

    1. Let visited set be « (url, "javascript") - ».

      2. - -

    2. Fetch the - descendants of and link result given settings object, - destination, visited set, and with an empty algorithm.

      3. -
    +

    If result is not null, optionally fetch the descendants of and link result given + settings object, destination, and an empty algorithm.

    -

    Generally, performing these steps will be beneficial for performance, as it +

    Generally, performing this step will be beneficial for performance, as it allows pre-loading the modules that will invariably be requested later, via algorithms such as fetch an external module script graph that fetch the entire graph. However, user agents might wish to skip them in bandwidth-constrained situations, or situations where the @@ -96260,12 +96206,9 @@ document.querySelector("button").addEventListener("click", bound);

  • If script is null, run onComplete given null, and return.

    • -

  • Let visited set be an empty set.

    • - -

  • Fetch the - descendants of and link script, given settings object, the - destination "script", visited set, and - onComplete.

    • +

  • Fetch the descendants of + and link script, given settings object, "script", and onComplete.

    • To fetch a module worker script graph @@ -96335,28 +96278,7 @@ document.querySelector("button").addEventListener("click", bound);

    This diagram illustrates how these algorithms relate to the ones above, as well as to each other:

    - - - + @@ -96374,7 +96296,7 @@ document.querySelector("button").addEventListener("click", bound); - fetch an import() module script graph + fetch a modulepreload module script graph @@ -96382,42 +96304,34 @@ document.querySelector("button").addEventListener("click", bound); - fetch a modulepreload module script graph + fetch an inline module script graph - - - fetch an inline module script graph - - - - - fetch a module worker script graph - + - + fetch a worklet script graph - + - + fetch a worklet/module worker script graph - + @@ -96425,23 +96339,6 @@ document.querySelector("button").addEventListener("click", bound); fetch the descendants of and link a module script - - - - - - fetch the descendants of a module script - - - - - - - - internal module script graph fetching procedure - - -

    To fetch a worklet/module worker script graph given a url, a fetch @@ -96473,211 +96370,86 @@ document.querySelector("button").addEventListener("click", bound);

  • If result is null, run onComplete given null, and abort these steps.

    • -

  • Let visited set be « (url, "javascript") - ».

    • - -

  • Fetch the - descendants of and link result given fetch client settings - object, destination, visited set, and - onComplete. If performFetch was given, pass it along as well.

    • +

  • Fetch the descendants + of and link result given fetch client settings object, + destination, and onComplete. If performFetch was given, pass + it along as well.

    • To fetch the descendants of and link a module script module - script, given a fetch client settings object, a destination, a - visited set, an onComplete algorithm, and an optional perform the fetch hook performFetch, run - these steps. onComplete must be an algorithm accepting null (on failure) or a - module script (on success).

    - -
      -
    1. -

      Fetch the descendants of - module script, given fetch client settings object, destination, - visited set, and onFetchDescendantsComplete as defined below. If - performFetch was given, pass it along as well.

      - -

      onFetchDescendantsComplete given result is the following algorithm:

      - -
        -
      1. -

        If result is null, then run onComplete given result, and - abort these steps.

        - -

        In this case, there was an error fetching one or more of the descendants. We - will not attempt to link.

        -
        2. - -

      2. Let parse error be the result of finding the first parse error - given result.

        3. - -
      3. -

        If parse error is null, then:

        - -
          -

        1. Let record be result's record.

          2. - -
        2. -

          Perform record.Link().

          - -

          This step will recursively call Link on all of - the module's unlinked dependencies.

          - -

          If this throws an exception, set result's error to rethrow to that exception.

          -
          3. -
        -
        4. - -

      4. Otherwise, set result's error - to rethrow to parse error.

        5. - -

      5. Run onComplete given result.

        6. -
      -
      2. -
    - -

    To fetch the descendants of a module script module script, given a - fetch client settings object, a destination, a visited set, an + script, given a fetch client settings object, a destination, an onComplete algorithm, and an optional perform the fetch hook performFetch, run these steps. onComplete must be an algorithm accepting null (on failure) or a module script (on success).

      -

    1. If module script's record is null, - run onComplete with module script and return.

      2. -

    2. Let record be module script's record.

      3. -

    3. If record is not a Cyclic Module Record, or if - record.[[RequestedModules]] is empty, run - onComplete with module script and return.

      4. - -

    4. Let moduleRequests be a new empty list.

      5. -
    5. -

      For each ModuleRequest Record - requested of record.[[RequestedModules]],

      +

      If record is null, then:

        -

      1. Let url be the result of resolving - a module specifier given module script and - requested.[[Specifier]].

        2. - -

      2. Assert: the previous step never throws an exception, because resolving a module specifier must have been previously successful with these same two - arguments.

        3. +

      3. Set module script's error to + rethrow to module script's parse error.

        4. -

      4. Let moduleType be the result of running the module type from module - request steps given requested.

        5. - -
      5. -

        If visited set does not contain - (url, moduleType), then:

        +

      6. Run onComplete given module script.

        7. -
          -

        1. Append requested to - moduleRequests.

          2. - -

        2. Append (url, moduleType) to - visited set.

          3. -
        - +

      7. Return.

      6. -

    6. Let options be the descendant script fetch options for module - script's fetch options.

      7. - -

    7. Assert: options is not null, as module script is a - JavaScript module script.

      8. +

    8. Let state be Record { [[ParseError]]: null, [[Destination]]: + destination, [[PerformFetch]]: null }.

      9. -

    9. Let pendingCount be the length of moduleRequests.

      10. +

    10. If performFetch was given, set state.[[PerformFetch]] to + performFetch.

      11. -

    11. If pendingCount is zero, run onComplete with module - script.

      12. +
    12. +

      Let loadingPromise be record.LoadRequestedModules(state).

      -

    13. Let failed be false.

      14. +

      This step will recursively load all the module transitive dependencies.

      +
    14. -

      For each moduleRequest in - moduleRequests, perform the internal module script graph fetching - procedure given moduleRequest, fetch client settings object, - destination, options, module script, visited set, - and onInternalFetchingComplete as defined below. If performFetch was - given, pass it along as well.

      - -

      onInternalFetchingComplete given result is the following algorithm:

      +

      Upon fulfillment of loadingPromise, run the following steps:

        -

      1. If failed is true, then abort these steps.

        2. - -

      2. If result is null, then set failed to true, run - onComplete with null, and abort these steps.

        3. +
      3. +

        Perform record.Link().

        -

      4. Assert: pendingCount is greater than zero.

        5. +

        This step will recursively call Link on all of + the module's unlinked dependencies.

        -

      5. Decrement pendingCount by one.

        6. +

        If this throws an exception, catch it, and set module script's error to rethrow to that exception.

        + -

      6. If pendingCount is zero, run onComplete with module - script.

        7. +

      7. Run onComplete given module script.

      - -

      The fetches performed by the internal module script graph fetching - procedure are performed in parallel to each other.

      15. -
    - -

    To perform the internal module script graph fetching procedure given a - moduleRequest, a fetch client settings object, a destination, - some options, a referringScript, a visited set, an - onComplete algorithm, and an optional perform the fetch hook performFetch, run - these steps. onComplete must be an algorithm accepting null (on failure) or a - module script (on success).

    - -
      -

    1. Let url be the result of resolving - a module specifier given referringScript and - moduleRequest.[[Specifier]].

      2. - -

    2. Assert: the previous step never throws an exception, because resolving a module specifier must have been previously successful with these same two - arguments.

      3. - -

    3. Let moduleType be the result of running the module type from module - request steps given moduleRequest.

      4. - -

    4. Assert: visited set contains - (url, moduleType).

    5. -

      Fetch a single module script given url, fetch client settings - object, destination, options, referringScript's - settings object, referringScript's base URL, moduleRequest, false, and - onSingleFetchComplete as defined below. If performFetch was given, pass - it along as well.

      - -

      onSingleFetchComplete given result is the following algorithm:

      +

      Upon rejection of loadingPromise, run the + following steps:

        -

      1. If result is null, run onComplete with null, and abort these - steps.

        2. +

      2. If state.[[ParseError]] is not null, set module script's error to rethrow to + state.[[ParseError]] and run onComplete given module + script.

        3. -

      3. Fetch the descendants of - result given fetch client settings object, destination, - visited set, and with onComplete. If performFetch was given, - pass it along as well.

        4. -
      +
    6. +

      Otherwise, run onComplete given null.

      -

      +

      state.[[ParseError]] is null when loadingPromise is + rejected due to a loading error.

      +
      7. +
    @@ -96696,12 +96468,11 @@ document.querySelector("button").addEventListener("click", bound); running the module type from module request steps given moduleRequest.

    -

  • Assert: the result of running the module type allowed steps - given moduleType 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 - fetch an import() module script graph.

    • +

  • Assert: the result of running the module type allowed steps given + moduleType 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 fetch a single imported module script.

  • Let moduleMap be module map settings object's module map.

    • @@ -96813,61 +96584,30 @@ document.querySelector("button").addEventListener("click", bound); -

    To find the first parse error given a root - moduleScript and an optional discoveredSet:

    +

    To fetch a single imported module script, given a url, a settings + object, a destination, some options, a referrer, a + moduleRequest, an onComplete algorithm, and an optional perform the fetch hook performFetch, run + these steps. onComplete must be an algorithm accepting null (on failure) or a + module script (on success).

      -

    1. Let moduleMap be moduleScript's settings object's - module map.

      2. - -

    2. If discoveredSet was not given, let it be an empty set.

      3. - -

    3. Append moduleScript to - discoveredSet.

      4. - -

    4. If moduleScript's record is null, - then return moduleScript's parse - error.

      5. - -

    5. If moduleScript's record is not a - Cyclic Module Record, then return null.

      6. - -

    6. Let moduleRequests be the value of moduleScript's record's [[RequestedModules]] internal slot.

      7. - -
    7. -

      For each moduleRequest of - moduleRequests:

      - -
        -

      1. Let childURL be the result of resolving a module specifier given moduleScript and - moduleRequest.[[Specifier]]. (This will never throw an exception, as otherwise - moduleScript would have been marked - as itself having a parse error.)

        2. - -

      2. Let moduleType be the result of running the module type from module - request steps given moduleRequest.

        3. - -

      3. Let childModule be moduleMap[(childURL, - moduleType)].

        4. - -

      4. Assert: childModule is a module script (i.e., it is - not "fetching" or null); by now all module - scripts in the graph rooted at moduleScript will have successfully been - fetched.

        5. - -

      5. If discoveredSet already contains - childModule, continue.

        6. +

      6. Assert: moduleRequest.[[Assertions]] does not contain any Record + entry such that entry.[[Key]] is not "type", because + we only asked for "type" assertions in + HostGetSupportedImportAssertions.

        7. -

      7. Let childParseError be the result of finding the first parse - error given childModule and discoveredSet.

        8. +

      8. Let moduleType be the result of running the module type from module + request steps given moduleRequest.

        9. -

      9. If childParseError is not null, return childParseError.

        10. -
      -
      8. +

    8. If the result of running the module type allowed steps given + moduleType and settings object is false, then run onComplete + given null, and return.

      9. -

    9. Return null.

      10. +

    10. Fetch a single module script given url, settings + object, destination, options, settings object, + referrer, moduleRequest, false, and onComplete. If + performFetch was given, pass it along as well.

    Creating scripts
    @@ -97054,7 +96794,7 @@ document.querySelector("button").addEventListener("click", bound);

    Run the steps to synchronously replace the rules of a CSSStyleSheet on sheet given source.

    -

    If this throws an exception, set script's If this throws an exception, catch it, and set script's parse error to that exception, and return script.

    @@ -97089,7 +96829,7 @@ document.querySelector("button").addEventListener("click", bound);

  • Let result be ParseJSONModule(source).

    -

    If this throws an exception, set script's If this throws an exception, catch it, and set script's parse error to that exception, and return script.

    • @@ -98759,9 +98499,8 @@ dictionary PromiseRejectionEventInit : EventInitAs a consequence, this means that when the import() expression is evaluated, there will still be no active script. Fortunately that is handled by our - implementations of HostResolveImportedModule and - HostImportModuleDynamically, by falling back to using the current settings - object's API base URL.

    + implementation of HostLoadImportedModule by falling back to using the + current settings object's API base URL.

    @@ -98797,8 +98536,8 @@ dictionary PromiseRejectionEventInit : EventInit.

    The returned promise will be rejected if an invalid specifier is given, or if a failure is - encountered while fetching or evaluating the resulting module graph.

    + encountered while fetching or evaluating the + resulting module graph.

    This syntax can be used inside both classic and module scripts. It thus provides a bridge into the module-script @@ -98882,8 +98621,8 @@ import "https://example.com/foo/../module2.mjs";

    This can result in two separate fetches and two separate module evaluations being performed. This is a willful violation of a constraint recommended (but not required) by the - import assertions specification stating that each call to HostResolveImportedModule - with the same (referencingScriptOrModule, moduleRequest.[[Specifier]]) pair + import assertions specification stating that each call to HostLoadImportedModule + with the same (referrer, moduleRequest.[[Specifier]]) pair must return the same Module Record.

    @@ -98955,169 +98694,185 @@ import "https://example.com/foo/../module2.mjs";

  • Let resolveFunction be ! CreateBuiltinFunction(steps, 1, "resolve", « »).

    • -

  • Return « Record { [[Key]]: "url", - [[Value]]: urlString }, Record { [[Key]]: "

    Return « Record { [[Key]]: "url", + [[Value]]: urlString }, Record { [[Key]]: "resolve", [[Value]]: resolveFunction } ».

    • -
    HostImportModuleDynamically(referencingScriptOrModule, - moduleRequest, promiseCapability)
    +
    HostGetSupportedImportAssertions()
    + +

    The Import Assertions proposal contains an implementation-defined + HostGetSupportedImportAssertions + abstract operation. User agents must use the following implementation:

    + +
      +

    1. Return « "type" ».

      2. +
    + +
    HostLoadImportedModule(referrer, + moduleRequest, loadState, payload)

    JavaScript contains an implementation-defined HostImportModuleDynamically abstract operation. - User agents must use the following implementation:

    + data-x="js-HostLoadImportedModule">HostLoadImportedModule     abstract operation. User agents + must use the following implementation:

    + +

    This specification expects the second parameter to be a ModuleRequest + Record, instead of a string as specified by ECMA-262. This is under the assumption that the + import assertions proposal, when updated to use HostLoadImportedModule + instead of the previous module loading hooks, will update the abstract operation passing a + ModuleRequest Record.

      -

    1. Let settings object be the current settings object.

      2. +

    2. Let settingsObject be the current settings object.

    3. -

      If settings object's global - object implements WorkletGlobalScope or - ServiceWorkerGlobalScope, then:

      +

      If settingsObject's global + object implements WorkletGlobalScope or ServiceWorkerGlobalScope + and loadState is undefined, then:

      + +

      loadState is undefined when the current fetching process has been + initiated by a dynamic import() call, either directly or when loading the + transitive dependencies of the dynamically imported module.

        -

      1. Let completion be Completion { [[Type]]: throw, [[Value]]: a new - TypeError, [[Target]]: empty }.

        2. +

      2. Let completion be Completion Record { [[Type]]: throw, + [[Value]]: a new TypeError, [[Target]]: empty }.

        3. -

      3. Perform FinishDynamicImport(referencingScriptOrModule, - moduleRequest, promiseCapability, completion).

        4. +

      4. Perform FinishLoadingImportedModule(referrer, + moduleRequest, payload, completion).

      5. Return.

      4. -

    4. Let referencing script be null.

      5. +

    5. Let referencingScript be null.

      6. -

    6. Let fetch options be the default classic script fetch +

    7. Let fetchOptions be the default classic script fetch options.

      8. +

    8. Let fetchReferrer be "client".

      9. +
    9. -

      If referencingScriptOrModule is not null, then:

      +

      If referrer is a Script Record or a Module Record, then:

        -

      1. Set referencing script to - referencingScriptOrModule.[[HostDefined]].

        +

      2. Set referencingScript to referrer.[[HostDefined]].

        -

      3. Set settings object to referencing script's settings +

      4. Set settingsObject to referencingScript's settings object.

        5. -

      5. Set fetch options to the descendant script fetch options for - referencing script's fetch +

      6. Set fetchOptions to the descendant script fetch options for + referencingScript's fetch options.

        7. -

      7. Assert: fetch options is not null, as referencing - script is a classic script or a JavaScript module +

      8. Assert: fetchOptions is not null, as + referencingScript is a classic script or a JavaScript module script.

        9. -
      - -

      As explained for HostResolveImportedModule, in the common - case, referencingScriptOrModule is non-null.

      -
      10. -
    10. -

      Fetch an import() module script graph given moduleRequest, - referencing script, settings object, fetch options, and with - the following steps given result:

      +
    11. +

      If neither of the following conditions are true:

      -
        -

      1. Let promise be null. +

          +
        • referrer is a Script Record; or
          • -

        • If result is null, then set promise to a promise rejected - with a new TypeError.

          • +
        • referrer is a Module Record and + referrer.[[Status]] is one of evaluating, evaluating-async or evaluated,
          • +
        -

      2. Otherwise, set promise to the result of running a module script given result and true.

        3. +

        then set fetchReferrer to referrer's base URL.

        -

      3. Perform FinishDynamicImport(referencingScriptOrModule, - moduleRequest, promiseCapability, promise).

        4. +

        We set fetchReferrer conditionally to not propagate the referrer + when using import(). Issue + #3744 looks into aligning dynamic imports with static imports.

        +
      -
      12. -
    - -
    HostResolveImportedModule(referencingScriptOrModule, - moduleRequest)
    -

    JavaScript contains an implementation-defined HostResolveImportedModule abstract operation. User - agents must use the following implementation:

    +
    +

    referrer is usually a Script Record or a Module Record, but it will not be so for event handlers per the get the current value of the event + handler algorithm. For example, given:

    -
      -

    1. Let moduleMap and referencingScript be null.

      2. + 
      <button onclick="import('./foo.mjs')">Click me</button>
      -
    2. -

      If referencingScriptOrModule is not null, then:

      +

      If a click event occurs, then at the time the + import() expression runs, GetActiveScriptOrModule will return null, + and this operation will receive the current realm as a fallback + referrer.

      +
    + -
      -

    1. Set referencingScript to - referencingScriptOrModule.[[HostDefined]].

      2. +

    2. Disallow further import maps given settingsObject.

      3. -

    3. Set moduleMap to referencingScript's settings - object's module map.

      4. -
    - +

  • Let url be the result of resolving a + module specifier given referencingScript and + moduleRequest.[[Specifier]], catching any exceptions. If they throw an exception, let + resolutionError be the thrown exception.

  • -

    Otherwise:

    +

    If the previous step threw an exception, then:

      -

    1. Assert: there is a current settings object.

      2. +

    2. Let completion be Completion Record { [[Type]]: throw, + [[Value]]: resolutionError, [[Target]]: empty }.

      3. -

    3. Set moduleMap to the current settings object's module map.

      4. -
    +

  • Perform FinishLoadingImportedModule(referrer, + moduleRequest, payload, completion).

    • -
    -

    referencingScriptOrModule is not usually null, but will be so for event handlers - per the get the current value of - the event handler algorithm. For example, given:

    +

  • Return.

    • + + - 
    <button onclick="import('./foo.mjs')">Click me</button>
    +

  • Let destination be "script".

    • -

    If a click event occurs, then at the time the - import() expression runs, GetActiveScriptOrModule will return null, - which will be passed to this abstract operation when HostResolveImportedModule is called by - FinishDynamicImport.

    -
    - +

  • If loadState is not undefined, then set destination to + loadState.[[Destination]].

    • -

  • Let url be the result of resolving a - module specifier given referencingScript and - moduleRequest.[[Specifier]].

    • +
  • +

    Fetch a single imported module script given url, settings + object, destination, fetchOptions, fetchReferrer, + moduleRequest, and onSingleFetchComplete as defined below. If + loadState is not undefined and loadState.[[PerformFetch]] is not null, + pass loadState.[[PerformFetch]] along as well.

    -

  • Assert: the previous step never throws an exception, because resolving a module specifier must have been - previously successful with these same two arguments (either while creating the corresponding module script, - or in fetch an import() module script graph).

    • +

    onSingleFetchComplete given moduleScript is the following + algorithm:

    -

  • Let moduleType be the result of running the module type from module - request steps given moduleRequest.

    • +
      +

    1. Let completion be null.

      2. -

    2. Let resolvedModuleScript be moduleMap[(url, - moduleType)]. (This entry must exist for us to have - gotten to this point.)

      3. +

    3. If moduleScript is null, then set completion to Completion + Record { [[Type]]: throw, [[Value]]: a new TypeError, [[Target]]: empty + }.

      4. -

    4. Assert: resolvedModuleScript is a module script - (i.e., is not null or "fetching").

      5. +
    5. +

      Otherwise, if moduleScript's parse + error is not null, then:

      -

    6. Assert: resolvedModuleScript's record is not null.

      +
        +

      1. Let parseError be moduleScript's parse error.

        2. -

      2. Return resolvedModuleScript's record.

        3. -
      +

    7. Set completion to Completion Record { [[Type]]: throw, + [[Value]]: parseError, [[Target]]: empty }.

      8. -
      HostGetSupportedImportAssertions()
      +

    8. If loadState is not undefined and loadState.[[ParseError]] is + null, set loadState.[[ParseError]] to parseError.

      9. +
    + -

    The Import Assertions proposal contains an implementation-defined - HostGetSupportedImportAssertions - abstract operation. User agents must use the following implementation:

    +

  • Otherwise, set completion to Completion Record { [[Type]]: + normal, [[Value]]: result's record, + [[Target]]: empty }.

    • -
      -

    1. Return « "type" ».

      2. +

    2. Perform FinishLoadingImportedModule(referrer, + moduleRequest, payload, completion).

      3. +
    + @@ -101085,9 +100840,8 @@ typedef OnBeforeUnloadEventHandlerNonNull? OnBeforeUnl

    In practice, this only affects the resolution of relative URLs via import(), which consult the base URL of the associated - script. Nulling out [[ScriptOrModule]] means that HostResolveImportedModule and - HostImportModuleDynamically will fall back to the current settings - object's API base URL.

    + script. Nulling out [[ScriptOrModule]] means that HostLoadImportedModule will + fall back to the current settings object's API base URL.

    diff --git a/styles.css b/styles.css index 5ad4abcc5c3..706560cec4f 100644 --- a/styles.css +++ b/styles.css @@ -111,6 +111,32 @@ td.eg { border-width: thin; text-align: center; } #abstractimg .horizontal, #abstractimg .left { word-spacing: 12px; font-size: 18px; text-anchor: middle; } #abstractimg .right { font-size: 25px; } +#module-script-fetching-diagram { + display: block; + margin: 0 auto; + width: 100%; + max-width: 1024px; +} + +#module-script-fetching-diagram rect { + stroke: black; + fill: transparent; +} + +#module-script-fetching-diagram path { + stroke: black; +} +#module-script-fetching-diagram path[marker-end] { + fill: transparent; +} + +#module-script-fetching-diagram a { + text-align: center; + display: flex; + align-items: center; + justify-content: center; +} + .jake-diagram { border-style: hidden none hidden hidden; table-layout: fixed;