- From: Ian Denhardt via GitHub <sysbot+gh@w3.org>
- Date: Thu, 21 Jan 2021 23:27:46 +0000
- To: public-webrtc-logs@w3.org
To make sure I understand your concern correctly: the issue is that `CanvasCaptureMediaStreamTrack` provides access to the underlying canvas object, and thus much of the other frame's DOM? I agree it's probably best not to include that. Perhaps we want to limit this to functionality provided by the `MediaStreamTrack` interface (not subclasses in general). Spitballing: maybe we could add a new type `TransferableMediaStreamTrack`, whose constructor wraps another `MediaStreamTrack` and makes it transferable, but only exposes "safe" functionality? (In this case only the tracks would be transferable, not the `MediaStream` as a whole -- but I don't think that's terribly limiting). -- GitHub Notification of comment by zenhack Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/158#issuecomment-765006615 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 21 January 2021 23:27:48 UTC