This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
An algorithm for entangling MessagePorts says that one may need to disentangle first, but nowhere it is defined how to disentangle ports. ---------------------------------- When the user agent is to entangle two MessagePort objects, it must run the following steps: If one of the ports is already entangled, then disentangle it and the port that it was entangled with. If those two previously entangled ports were the two ports of a MessageChannel object, then that MessageChannel object no longer represents an actual channel: the two ports in that object are no longer entangled. Associate the two ports to be entangled, so that they form the two parts of a new channel. (There is no MessageChannel object that represents this channel.) ----------------------------------
What would the steps be? "When the user agent is to disentangle two MessagePort objects, it must run the following steps: 1. Disassociate the two ports to no longer be entangled." That's more words, but I don't see what more it says than just "disentangle".
It would be helpful to define "associate" and "disassociate" too. It's completely non-obvious to me what these mean when the ports are in separate threads or processes. Does this mean something like "post a message to disassociate"?
Isn't that just an implementation detail?
Checked in as WHATWG revision r7892. Check-in comment: Let's try some more explanatory text http://html5.org/tools/web-apps-tracker?from=7891&to=7892
marking fixed based on irc comments; feel free to reopen if you have any ideas how to make this better.