- From: stefan hakansson via GitHub <sysbot+gh@w3.org>
- Date: Wed, 22 Nov 2017 07:34:11 +0000
- To: public-webrtc-logs@w3.org
@fippo I note that not only would we need order (to know which is 'first'), but also keep track of which transceivers are 'new' as the behavior specified by [JSEP a long time ago](https://github.com/w3c/webrtc-pc/issues/1586#issuecomment-3460708949) says the setting does not apply to negotiated transceivers. JSEP at the time however said that all 'fresh' transceivers with an associated outgoing track should be marked as ```sendonly``` if offerToRecieveX is either false or 0, so that seems to take away the need to identify which is 'first'. How many implementations support this today? -- GitHub Notification of comment by stefhak Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1586#issuecomment-346266682 using your GitHub account
Received on Wednesday, 22 November 2017 07:34:15 UTC