Open Bug 1874820 Opened 1 year ago Updated 1 year ago

Implementation of close event of MessagePort API

Categories

(Core :: DOM: Core & HTML, enhancement)

enhancement

Tracking

()

People

(Reporter: murakinonoka, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: dev-doc-needed)

User Agent: Mozilla/5.0 (X11; CrOS x86_64 14541.0.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36

Steps to reproduce:

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: https://github.com/whatwg/html/issues/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: https://github.com/mozilla/standards-positions/issues/914
WebKit standards position: https://github.com/WebKit/standards-positions/issues/271
HTML spec PR: https://github.com/whatwg/html/pull/9933

(In reply to nonoka from comment #0)

User Agent: Mozilla/5.0 (X11; CrOS x86_64 14541.0.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36

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: https://github.com/whatwg/html/issues/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: https://github.com/mozilla/standards-positions/issues/914
WebKit standards position: https://github.com/WebKit/standards-positions/issues/271
HTML spec PR: https://github.com/whatwg/html/pull/9933

The Bugbug bot thinks this bug should belong to the 'Core::DOM: Core & HTML' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → DOM: Core & HTML
Product: Firefox → Core
Blocks: html
Status: UNCONFIRMED → NEW
Ever confirmed: true
You need to log in before you can comment on or make changes to this bug.