Re: [webrtc-pc] Can we have non-origin-clean MediaStreamTracks? (#2397)

This quote is there for addTrack, we should probably add it to addTransceiver as well or move it to some section that talks about any tracks

> A track could have contents that are inaccessible to the application. This can be due to anything that would make a track CORS cross-origin. These tracks can be supplied to the addTrack() method, and have an RTCRtpSender created for them, but content MUST NOT be transmitted. Silence (audio), black frames (video) or equivalently absent content is sent in place of track content.
> 
> Note that this property can change over time.

-- 
GitHub Notification of comment by henbos
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2397#issuecomment-681993854 using your GitHub account


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

Received on Thursday, 27 August 2020 14:43:27 UTC