- From: guidou via GitHub <sysbot+gh@w3.org>
- Date: Mon, 25 Jan 2021 14:34:27 +0000
- To: public-webrtc-logs@w3.org
If one were to transfer a MediaStreamTrack to an iframe with a different origin, wouldn't that make the transferred track a track with cross-origin content (from the perspective of the iframe)? If that's the case, what should be done with such a track? mediacapture-main does not mention this possibility because it focuses on webcam and mic which can't be considered cross origin, but mediacapture-fromelement can and it says that "attempting to transfer the media using WebRTC results in no information being transmitted", and similar things for other APIs. Chromium does not even support these "tainted" tracks. When a track becomes cross origin, it stops. Wrt the possibility of prototyping this using Breakout Box, the transferability of VideoFrames in Chromium is limited to same-origin/same-process cases, so it's not possible to produce a useful shim using the approach @youennf proposes in https://github.com/w3c/mediacapture-screen-share/issues/158#issuecomment-765565070 . Full transferability to cross-origin (and potentially cross-process) requires more complex mechanisms such as @martinthomson mentions in https://github.com/w3c/mediacapture-screen-share/issues/158#issuecomment-765815053. -- GitHub Notification of comment by guidou Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/158#issuecomment-766857651 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 25 January 2021 14:34:39 UTC