#923: Adding a close event to MessagePort API

Visit on Github.

Opened Dec 19, 2023

こんにちは TAG-さん!

I'm requesting a TAG review of a close event of MessagePort API.

This is a proposal to add a close event which notifies one of the MessagePorts that the other port has been disentangled (i.e., close() is called, an owning document is destroyed, or the port is garbage collected).

Further details:

  • I have reviewed the TAG's Web Platform Design Principles
  • Relevant time constraints or deadlines: My intern term will end on 1/19, so It would greatly benefit our efforts if we could receive reviews as soon as possible.
  • The group where the work on this specification is currently being done: WHATWG
  • The group where standardization of this work is intended to be done (if current group is a community group or other incubation venue): WHATWG
  • Major unresolved issues with or opposition to this specification: N/A
  • This work is being funded by: Google

You should also know that...

[please tell us anything you think is relevant to this review]

We'd prefer the TAG provide feedback as (please delete all but the desired option):

🐛 open issues in our GitHub repo for each point of feedback

☂️ open a single issue in our GitHub repo for the entire review

💬 leave review feedback as a comment in this issue and @-notify @nononokam

Discussions

2024-01-15

Minutes

Dan: can we close this? It's small. It's about adding one specific piece of functionality, related to bfcache. Wanted to make sure Tess has visibility. Propose close?

Peter: okay with that

agreed to revisit at the plenary

2024-01-london

Minutes

Dan: Can we close?

Tess: not great but... in the s&p answers it says - it exposes when GC happens.. but that might be unavoidable. It's fine...

we agree to close with satisfied