diff --git a/source b/source index 53a123e70a7..398ad1ffafd 100644 --- a/source +++ b/source @@ -2493,6 +2493,7 @@ a.setAttribute('href', 'https://example.com/'); // change the content attribute
  • safely extracting a body
  • processResponseConsumeBody
  • processResponseEndOfBody
    • +
  • consume body
  • response and its @@ -4186,6 +4187,19 @@ a.setAttribute('href', 'https://example.com/'); // change the content attribute + + +
    WebAssembly JavaScript Module Integration
    + +
    +

    The following terms are defined in WebAssembly JavaScript Module Integration:

    + + +
    +
    @@ -91620,6 +91634,9 @@ document.querySelector("button").addEventListener("click", bound);

  • a Synthetic Module Record, for CSS module scripts and JSON module scripts

    • +

  • a WebAssembly Module Record, for WebAssembly module scripts;

    • +

  • null, representing a parsing failure.

    • @@ -91691,6 +91708,10 @@ document.querySelector("button").addEventListener("click", bound); its record is a Source Text Module Record.

    +

  • A module script is a WebAssembly module script if + its record is a WebAssembly Module + Record.

    • +

  • A module script is a CSS module script if its record is a Synthetic Module Record, and it @@ -92705,6 +92726,22 @@ document.querySelector("button").addEventListener("click", bound); creating a JSON module script given source text and module map settings object.

    • +

  • If the MIME type essence of MIME type is + "application/wasm" and module type is "javascript", then:

    +
      +

    1. Let bufferPromise be the result of running consume body on + response with ArrayBuffer.

      2. + +

    2. Create a WebAssembly module + script given bufferPromise, module map settings object, + response's url, and options. + Wait until the algorithm asynchronously completes with result.

      3. + +

    3. Set module script to result.

      4. +
    +
    • +

  • Set moduleMap[(url, moduleType)] to module script, and asynchronously complete this algorithm @@ -92890,36 +92927,12 @@ document.querySelector("button").addEventListener("click", bound); we only asked for "type" assertions in HostGetSupportedImportAssertions.

    • -
  • -

    For each ModuleRequest record - requested of result.[[RequestedModules]]:

    - -
      -

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

      2. - -

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

      3. +

    3. Run the validate requested module specifiers steps given result + and script.

      -
    4. -

      If url is failure, or if the result of running the module type - allowed steps given moduleType and settings is false, then:

      -
        -

      1. Let error be a new TypeError exception.

        2. - -

      2. Set script's parse error - to error.

        3. - -

      3. Return script.

        4. -
      -
      5. -
    - -

    This step is essentially validating all of the requested module specifiers and - type assertions. We treat a module with unresolvable module specifiers or unsupported type - assertions the same as one that cannot be parsed; in both cases, a syntactic issue makes it - impossible to ever contemplate linking the module later.

    +

    If these steps throw an exception, set script's parse error to that exception, and return + script.

  • Set script's record to @@ -92996,6 +93009,109 @@ document.querySelector("button").addEventListener("click", bound);

  • Return script.

    • +

    To create a WebAssembly module script, + given a promise that will resolve with an ArrayBuffer + bufferPromise, an environment settings object settings, a + URL baseURL, and some script fetch options + options, run these steps. The algorithm will asynchronously complete with a new + WebAssembly module script.

    + +
      +

    1. If scripting is disabled for + settings, then set bufferPromise to a promise resolved with an empty + ArrayBuffer.

      2. + + +

    2. Let script be a new WebAssembly module script that this algorithm + will subsequently initialize.

      3. + +

    3. Set script's settings object to settings.

      4. + +

    4. Set script's base URL to + baseURL.

      5. + +

    5. Set script's fetch + options to options.

      6. + +

    6. Set script's parse error and + error to rethrow to null.

      7. + +
    7. +

      Upon fulfillment of bufferPromise with buffer:

      + +
        +
      1. +

        Let module be the result of parse a WebAssembly module given + buffer, settings's Realm, and script.

        + +

        Passing script as the last parameter here ensures + result.[[HostDefined]] will be script.

        + +

        If this algorithm throws an exception, set script's parse error to that exception, and asynchronously + complete this algorithm with script.

        +
        2. + +

      2. Run the validate requested module specifiers steps given module + and script.

        + +
        3. + +

      3. Set script's record to + module.

        4. + +

      4. Asynchronously complete this algorithm with script.

        5. +
      +
      8. + +
    8. +

      Upon rejection of bufferPromise with reason:

      +
        +

      1. Set script's parse error to + reason.

        2. + +

      2. Asynchronously complete this algorithm with script.

        3. +
      +
      9. +
    + +

    The validate requested module specifiers + steps, given a module record record and a script script, are as + follows:

    + +
      +
    1. +

      For each ModuleRequest record + requested of record.[[RequestedModules]]:

      + +
        +

      1. Let url be the result of resolving + a module specifier given script's base + URL and requested.[[Specifier]].

        2. + +

      2. Let moduleType be the result of running the module type from module + request steps given requested.

        3. + +
      3. +

        If url is failure, or if the result of running the module type + allowed steps given moduleType and settings is false, then:

        + +
          +

        1. Let error be a new TypeError exception.

          2. + +

        2. Throw error.

          3. +
        +
        4. +
      +
      2. +
    + +

    These steps are essentially validating all of the requested module specifiers and + type assertions. We treat a module with unresolvable module specifiers or unsupported type + assertions the same as one that cannot be parsed; in both cases, a syntactic issue makes it + impossible to ever contemplate linking the module later.

    +

    The module type from module request steps, given a ModuleRequest Record moduleRequest, are as follows:

    @@ -126668,6 +126784,9 @@ INSERT INTERFACES HERE
    application/xml
    XML
    +
    application/wasm
    +
    WebAssembly
    +
    image/gif
    GIF images
    @@ -127314,6 +127433,12 @@ INSERT INTERFACES HERE
    [WASMJS]
    (Non-normative) WebAssembly JavaScript Interface, D. Ehrenberg. W3C.
    +
    [WASM]
    +
    WebAssembly Core Specification, A. Rossberg. W3C.
    + +
    [WASMESM]
    +
    WebAssembly JavaScript Module Integration, L. Clark, D. Ehrenberg. W3C.
    +
    [WCAG]
    (Non-normative) Web Content Accessibility Guidelines (WCAG), A. Kirkpatrick, J. O Connor, A. Campbell, M. Cooper. W3C.