1129904 - Implement PortCollection

Status: RESOLVED INVALID

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

Description

[Andrea Marchesini [:baku]]

Attachment: portcollection.patch

This is a low low priority API related to MessagePort/MessageChannel. I had this code on my laptop and I guess would be nice to land it.
It already supports workers, but we cannot enable it until MessagePort/MessageChannel on workers is not landed.

Comment 1

[Boris Zbarsky [:bzbarsky]]

Comment on attachment 8559767 [details] [diff] [review]
portcollection.patch

Why does this use "iterate" instead of, say, forEach?  Or just having an ES6 iterator?

Comment 2

[Andrea Marchesini [:baku]]

Good point. Probably we should file a bug for the spec. I'll ping annevk.
Btw, we don't have iterable<> support in WebIDL yet, right?

Comment 3

[Olli Pettay [:smaug][[e-mail]]]

https://html.spec.whatwg.org/multipage/comms.html#broadcasting-to-many-ports

"The API described in this section is controversial, as, in an attempt to solve an architectural memory leak, it instead exposes the details of Garbage Collection. This is a lose-lose scenario. A better solution is really needed here."

Comment 4

[Olli Pettay [:smaug][[e-mail]]]

Comment on attachment 8559767 [details] [diff] [review]
portcollection.patch

So I think we should not implement PortCollection as it is defined currently.

Comment 5

[Anne (:annevk)]

Note https://www.w3.org/Bugs/Public/show_bug.cgi?id=23412 filed by Olli.

Comment 6

[Boris Zbarsky [:bzbarsky]]

> Btw, we don't have iterable<> support in WebIDL yet, right?

No, but we should add it.

Comment 7

[Andrea Marchesini [:baku]]

PortCollection has been removed by the spec.