Skip to content

In-flight MessagePort behavior #12490

@francovs

Description

@francovs

While a MessagePorts object is transferred, disentanglement of the old MessagePort object happens on the receiving side (on the "transfer-receiving steps"), not on the sending side.

This means MessagePort objects can be in an intermediate "shipped but not yet disentangled" state - the "has been shipped" flag and the Detached internal slot are both set, but disentanglement didn't happen yet.

Should ports still be able to postMessage(), or run onmessage handlers, while in this state? More generally, should this state be observable at all? (I assuming no, because it would involve the receiving side atomically yoinking the port away from the sending side)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions