Re: [mediacapture-handle] Expose a MessagePort using Capture Handle (#70)

P.S:

> postMessage handles this with MessageEvent.source.

Won't we need to modify the MessagePort spec in some way to ensure that `CaptureController.onmessage`, which is proposed in [this comment](https://github.com/w3c/mediacapture-handle/issues/70#issuecomment-1406345920), is the target of `MessageEvent.source`?

Do we really want `CaptureController` to expose `postMessage()` and `onmessage`? Should we not have it just expose a `port`? (I don't support this proposal of yours, but I'd like to not-support the best possible version of it... :-))

-- 
GitHub Notification of comment by eladalon1983
Please view or discuss this issue at https://github.com/w3c/mediacapture-handle/issues/70#issuecomment-1479844072 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 22 March 2023 16:00:36 UTC