I updated https://github.com/w3c/webrtc-pc/pull/2390 to leave some of the text. It seems the only case that could have cross origin MediaStreamTrack is video element capture. It seems best for the video element capture to define how these tracks should behave (i.e. do not provide content except to video elements). This is already done in https://w3c.github.io/mediacapture-fromelement/#security-considerations: "attempting to transfer the media using WebRTC [WEBRTC] results in no information being transmitted". I would prefer we tighten the wording there instead of webrtc-pc (current webrtc-pc wording is vague and difficult to understand without context). FWIW, WebAudio is not defining anything special here, this seems fine to me. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2397#issuecomment-562477477 using your GitHub accountReceived on Friday, 6 December 2019 08:17:23 UTC
This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:49 UTC