- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Fri, 21 Feb 2020 21:43:18 +0000
- To: public-webrtc-logs@w3.org
JSEP and RtpTransceivers live in the "in parallel" world, the non-JS thread. RTCRtpTransceiver live in the JS thread. They should be treated as separate - as such, JSEP modifying transceivers in parallel is not an issue. If we have any references from a JS objects to return a state of a non-JS object we have a spec bug. For example: > The mid attribute is the media stream "identification-tag" negotiated and present in the local and remote descriptions as defined in [JSEP] (section 5.2.1. and section 5.3.1.). I read this as a non-normative description of what could only reasonably be implemented with an internal slot. The fact that this is not saying "Return the value of the [[\Mid]] internal slot." here and "Set the value of transceiver's [[\Mid]] to the corresponding media stream "identification-tag"" is a spec bug. -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2476#issuecomment-589849628 using your GitHub account
Received on Friday, 21 February 2020 21:43:20 UTC