From b1aba94df1bd8db8dd6622c6df8a0f571d8db84b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Nicol=C3=B2=20Ribaudo?= Date: Tue, 5 Nov 2024 12:17:01 +0100 Subject: [PATCH] Do the same for DedicatedWorkerGlobalScope (the other side) --- source | 23 +++++++++++++++-------- 1 file changed, 15 insertions(+), 8 deletions(-) diff --git a/source b/source index 11c4691f493..d39c6ad9b74 100644 --- a/source +++ b/source @@ -119752,13 +119752,10 @@ interface DedicatedWorkerGlobalScope : WorkerGlobalSc DedicatedWorkerGlobalScope includes MessageEventTarget; -

DedicatedWorkerGlobalScope objects act as if they had an implicit - MessagePort associated with them. This port is part of a channel that is set up when - the worker is created, but it is not exposed. This object must never be garbage - collected before the DedicatedWorkerGlobalScope object.

- -

All messages received by that port must immediately be retargeted at the - DedicatedWorkerGlobalScope object.

+

DedicatedWorkerGlobalScope objects has an associated inside port (a + MessagePort). This port is part of a channel that is set up when the worker is + created, but it is not exposed. This object must never be garbage collected before + the DedicatedWorkerGlobalScope object.

dedicatedWorkerGlobal.name
@@ -120170,7 +120167,17 @@ interface SharedWorkerGlobalScope : WorkerGlobalScope inside settings's realm.

-

  • Associate inside port with worker global scope.

    • +
  • +

    If shared is false, then:

    + +
      +

    1. Set inside port's message event target to worker global + scope.

      2. + +

    2. Set worker global scope's inside port to inside + port.

      3. +
    +

  • Entangle outside port and inside port.