- From: stefan hakansson via GitHub <sysbot+gh@w3.org>
- Date: Wed, 17 Jan 2018 09:51:09 +0000
- To: public-webrtc-logs@w3.org
@jan-ivar sorry for derailing (I agree this is not the scope of this Issue), but for clarity the spec now says that (assume a stable state, a "sendrecv" pair of transceivers (one at each endpoint), the remote track event has been fired): - setting direction to "recvonly", followed by SDP O/A, would (when the offer is set at the remote side) give a "mute" event on that remote track - then, changing direction back to "sendrecv" followed by SDP O/A, would (when the offer is set at the remote side) give a "track" event on the remote PeerConnection This is not what I would have expected, I would (naïvely) have expected an "unmute" event on the track. I have no desire to propose changes if this is what have agreed on, it just seems strange. BTW, in this example, what would the mute attribute of the track of the track event read? -- GitHub Notification of comment by stefhak Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1729#issuecomment-358252595 using your GitHub account
Received on Wednesday, 17 January 2018 09:51:11 UTC