diff --git a/source b/source index 042d5e686d8..2dd281067d8 100644 --- a/source +++ b/source @@ -87022,10 +87022,9 @@ interface NavigatorOnLine {
  • Asynchronously complete this algorithm with script.
    • -

    To fetch a classic worker script given a url, a referrer, a - settings object, and a destination, run these steps. The algorithm will - asynchronously complete with either null (on failure) or a new classic script (on - success).

    +

    To fetch a classic worker script given a url, a settings + object, and a destination, run these steps. The algorithm will asynchronously + complete with either null (on failure) or a new classic script (on success).

    1. Let request be a new request whose @@ -87033,7 +87032,6 @@ interface NavigatorOnLine { data-x="concept-request-client">client is settings object, type is "script", destination is destination, referrer is referrer, mode is "same-origin", credentials mode is "same-origin", parser @@ -96681,10 +96679,9 @@ interface WorkerGlobalScope : EventTarget {

      When a user agent is to run a worker for a script with Worker or SharedWorker object worker, URL - url, URL referrer, MessagePort outside - port, list of relevant Document objects to add docs, - possible WorkerGlobalScope parent worker global scope, and a - WorkerOptions dictionary options, it must run the following steps:

      + url, environment settings object outside settings, + MessagePort outside port, and a WorkerOptions dictionary + options, it must run the following steps:

        @@ -96701,6 +96698,16 @@ interface WorkerGlobalScope : EventTarget {

      1. Let is shared be true if worker is a SharedWorker object, and false otherwise.

        2. +

      2. Let docs be the list of relevant Document objects to + add given outside settings.

        3. + +

      3. Let parent worker global scope be null.

        + +

      4. If outside settings's global + object is a WorkerGlobalScope object (i.e. we are creating a nested worker), + set parent worker global scope to outside settings's global object.

        5. +

      5. Call the JavaScript InitializeHostDefinedRealm() abstract @@ -96729,14 +96736,14 @@ interface WorkerGlobalScope : EventTarget {

        "classic"
        -
        Fetch a classic worker script given url, referrer, - settings object, and destination.
        +
        Fetch a classic worker script given url, outside + settings, and destination.
        "module"
        Fetch a module script tree given url, the value of the credentials member of options, the empty string (as no cryptographic nonce is present for workers), "not - parser-inserted", destination, and settings object.
        + parser-inserted", destination, and outside settings.

        In both cases, to process the @@ -97224,31 +97231,23 @@ enum WorkerType { "classic", "module" }; data-x="blob protocol">blob: URLs.

        6. +

      6. Let outside settings be the incumbent settings object.

        +

      7. Let worker be a new Worker object.

      8. Create a new MessagePort object whose owner is the incumbent settings object. Let this - be the outside port.

        9. + data-x="concept-port-owner">owner is outside settings. Let this be the + outside port.

      9. Associate the outside port with worker.

      10. Let docs be the list of relevant Document objects to - add given the incumbent settings object.

        11. - -

      11. Let parent worker global scope be null.

        12. - -

      12. If the global object specified by the - incumbent settings object is a WorkerGlobalScope object (i.e. we are - creating a nested worker), set parent worker global scope to the - WorkerGlobalScope object that is the global object specified by the incumbent - settings object.

        13. + add given outside settings.

      13. Return worker, and run the following step in parallel.

        14. -

      14. Run a worker given worker, worker URL, the - incumbent settings object's creation URL, outside port, - docs, parent worker global scope, and options.

        15. +

      15. Run a worker given worker, worker URL, outside + settings, outside port, and options.

      @@ -97290,7 +97289,6 @@ interface SharedWorker : EventTarget { the following steps:

        -

      1. The user agent may throw a SecurityError exception and abort these steps if the request violates a policy decision (e.g. if the user agent is configured to not allow the page to start shared workers).

        2. @@ -97308,12 +97306,7 @@ interface SharedWorker : EventTarget { data-x="blob protocol">blob: URLs.

        -
      2. - -

        Let docs be the list of relevant Document objects to - add given the incumbent settings object.

        - -
        3. +

      3. Let outside settings be the incumbent settings object.

      4. @@ -97324,8 +97317,8 @@ interface SharedWorker : EventTarget {

      5. Let worker be a new SharedWorker object.

      6. Create a new MessagePort object whose owner is the incumbent settings object. Let - this be the outside port.

        7. + data-x="concept-port-owner">owner is outside settings. Let this be the + outside port.

      7. Assign outside port to the port attribute of worker.

        8. @@ -97340,27 +97333,23 @@ interface SharedWorker : EventTarget { SharedWorkerGlobalScope object.

      8. -

        If worker global scope is not null, but the user agent has been - configured to disallow communication between the worker represented by the worker global scope and the scripts whose - settings objects are the incumbent settings - object, then set worker global scope to null.

        + configured to disallow communication between the worker represented by the worker global + scope and the scripts whose settings object is outside settings, then set worker global + scope to null.

        For example, a user agent could have a development mode that isolates a particular top-level browsing context from all other pages, and scripts in that development mode could be blocked from connecting to shared workers running in the normal browser mode.

        -
      9. -

        If worker global scope is not null, then run these steps:

          - -

        1. Associate worker with worker global - scope.

          2. +

        2. Associate worker with worker global scope.

        3. Let settings object be the relevant settings object for worker global scope.

          4. @@ -97369,8 +97358,7 @@ interface SharedWorker : EventTarget { data-x="concept-port-owner">owner is settings object. Let this be the inside port.

          -

        4. Entangle outside port - and inside port.

          5. +

        5. Entangle outside port and inside port.

        6. Create a trusted event that uses the MessageEvent interface, with the name SharedWorker : EventTarget { source, to dispatch the event at worker global scope.

          7. -
        7. - -

          Add to worker global - scope's list of the worker's Documents the - Document objects in docs.

          - -
          8. - -
        8. - -

          If the global object specified by - the incumbent settings object is a WorkerGlobalScope object, add - worker global scope to the list of the worker's workers of the - WorkerGlobalScope object that is the global object specified by the - incumbent settings object.

          +

        9. Add to worker global + scope's list of the worker's Documents the + list of relevant Document objects to add given outside + settings.

          10. - +

        10. If outside settings's global + object is a WorkerGlobalScope object, add worker global scope + to the list of the worker's workers of outside settings's global object.

        11. Return worker and abort all these steps.

          12. -
        -
        10. - - - -

      10. Let parent worker global scope be null.

        11. - -

      11. If the global object specified by - the incumbent settings object is a WorkerGlobalScope object (i.e. we - are creating a nested worker), set parent worker global scope to the - WorkerGlobalScope object that is the global object specified by the incumbent - settings object.

      -

    2. Return worker and perform the remaining steps in parallel.

      3. -

    3. Run a worker given worker, urlRecord, the - incumbent settings object's creation URL, outside port, - docs, parent worker global scope, and options.

      4. +

    4. Run a worker given worker, urlRecord, outside + settings, outside port, and options.