Skip to content

Add clarification about context propagation into worklets #136

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 7, 2025
Merged

Add clarification about context propagation into worklets #136

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions WEB-INTEGRATION.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -568,6 +568,13 @@ calling those methods), in practice that context will always match the root cont
worklet scope (because `register*()` is always called at the top-level). Hence, to simplify
implementations we propose that Worklet methods always run in the root context.

According to the HTML spec, creating a worklet global scope always creates a new agent, and
therefore there can't be any propagation from other context into the worklet and vice versa, even
if its event loop runs in the same thread as other agents. This isn't always implemented this way –
in Chromium, for example, the equivalent of an agent is shared among worklets and other agents
running in the same thread; but since this agent sharing is unobservable, we should not add a
dependency on it.

### Custom elements

Custom elements are also registered by passing a class to a web API, and this class
Expand Down