W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > February 2023

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

From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
Date: Thu, 02 Feb 2023 16:38:38 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-1414035579-1675355917-sysbot+gh@w3.org>
I like the minimal API in https://github.com/w3c/mediacapture-handle/issues/70#issuecomment-1406345920 on the controller, assuming `postMessage` is modeled on the one from [Window](https://html.spec.whatwg.org/multipage/nav-history-apis.html#the-window-object:dom-window-postmessage): 
partial interface CaptureController {
  undefined postMessage(any message, USVString targetOrigin, optional sequence<object> transfer = []);
  undefined postMessage(any message, optional WindowPostMessageOptions options = {});
That way, apps have `targetOrigin` to deal with navigation in the capturee.

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

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 2 February 2023 16:38:40 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:20:00 UTC