Bug 267567

Summary:	Implementation of close event of MessagePort API
Product:	WebKit	Reporter:	nonoka <murakinonoka>
Component:	DOM	Assignee:	Nobody <webkit-unassigned>
Status:	NEW ---
Severity:	Normal	CC:	annevk, cdumez, itsmings, karlcow, mike, rakina, webkit-bug-importer, youennf
Priority:	P2	Keywords:	BrowserCompat, InRadar
Version:	WebKit Nightly Build
Hardware:	Unspecified
OS:	Unspecified

Description nonoka 2024-01-15 23:12:43 PST

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

Comment 1 Radar WebKit Bug Importer 2024-01-22 23:13:15 PST

<rdar://problem/121416714>

Comment 2 Anne van Kesteren 2024-06-06 22:32:56 PDT

This should not be implemented until https://github.com/whatwg/html/issues/10201 is resolved.