Skip to content
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.

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

Implementation of close event of MessagePort API #21964

Open
nononokam opened this issue Jan 17, 2024 · 0 comments
Open

Implementation of close event of MessagePort API #21964

nononokam opened this issue Jan 17, 2024 · 0 comments
Labels
feat new feature (which has been agreed to/accepted) web related to Web APIs

Comments

@nononokam
Copy link

nononokam commented Jan 17, 2024

Proposal

There was no timely and reliable way to detect when a MessagePort becomes disentangled, which made it difficult to release resources associated with ports.
We proposed to add a close event to MessagePort API.
The close event has landed to the HTML spec. Chrome has already completed implementation and it’s close to ship.

Initial issue: whatwg/html#1766
Explainer: https://github.com/fergald/explainer-messageport-close
HTML spec: https://html.spec.whatwg.org/multipage/web-messaging.html#disentangle
Chrome status: https://chromestatus.com/feature/5086799659794432
Mozilla standards position: mozilla/standards-positions#914
WebKit standards position: WebKit/standards-positions#271
HTML spec PR: whatwg/html#9933

Primary contacts: @rakina, @mingyc, @nononokam

@lucacasonato lucacasonato added feat new feature (which has been agreed to/accepted) web related to Web APIs labels Jun 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feat new feature (which has been agreed to/accepted) web related to Web APIs
Projects
None yet
Development

No branches or pull requests

2 participants