#923: Adding a close event to MessagePort API
Discussions
Discussed
Jan 1, 2024 (See Github)
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
Discussed
Jan 15, 2024 (See Github)
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
Comment by @hober Jan 23, 2024 (See Github)
Hi @nononokam!
@torgo @LeaVerou @matatk and I looked at this today and we think this looks pretty good! I'm a little worried about this sort-of exposing GC timing sometimes, but you've already considered that and have ended up in a reasonable place.
OpenedDec 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:
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