You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add pausing execution of worklets and dedicated workers
The lifecycle of workers and worklets was undefined in the specification.
Add some formalization around dedicated workers and worklets. Still to
be determined is what happens with shared workers and service workers.
Any [=worklet agent=] whose single [=/realm=]'s [=Realm/global object=]'s [=worklet/owning document=] is [=/frozen=] must become [=blocked=].
193
+
Any [=dedicated worker agent=] whose single [=/realm=]'s [=Realm/global object=]'s [=DedicatedWorkerGlobalScope/owning document=] is non-null and [=/frozen=] must become [=blocked=].
194
+
195
+
<div algorithm>
196
+
To determine the <dfn for="DedicatedWorkerGlobalScope" export>owning document</dfn> for a {{DedicatedWorkerGlobalScope}} |workerGlobalScope|:
197
+
198
+
1. If |workerGlobalScope|'s [=owner set=] consists of a single {{Document}} |document|, then return |document|.
199
+
1. If |workerGlobalScope|'s [=owner set=] consists of a single {{DedicatedWorkerGlobalScope}} |parentWorkerGlobalScope|, then return |parentWorkerGlobalScope|'s [=owning document=].
200
+
1. Return null.
201
+
202
+
NOTE: A {{DedicatedWorkerGlobalScope}}'s [=owner set=] will always have exactly one item.
0 commit comments