js/wasm: introduce scope for JS object #72786

romaindoumenc · 2025-03-11T09:01:23Z

This changes allow to attach a JS object (e.g. browser component) to a
js/wasm Go program. This creates a scope to only capture relevant events,
enabling Web applications mixing Go / native components.

An example use is discussed in the GitHub issue.

Implementation-wise, this contains two changes:

on the JS side the go object gets a new field 'scope' that is checked
on the Go side, in package syscall/js, func Scope() Value returns
go.scope when it has been provided, or else window/global.

A small test uses a dummy object to perform a simple get/set action on this
new field.

Fixes #56084

gopherbot · 2025-03-11T09:06:10Z

This PR (HEAD: ef681aa) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/656595.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2025-03-11T10:01:50Z

Message from Jorropo:

Patch Set 1: Commit-Queue+1