W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > September 2017

Re: [webrtc-pc] Inconsistent setting of receiver.track.readyState violates Mediacapture

From: Taylor Brandstetter via GitHub <sysbot+gh@w3.org>
Date: Thu, 07 Sep 2017 20:44:08 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-327922351-1504817039-sysbot+gh@w3.org>
> I'd say this whole paragraph belongs under set an RTCSessionDescription, not under stop().

You mean the paragraph that says:

> When a remote description is applied with a zero port in the media description for the corresponding transceiver, as defined in [JSEP] (section 4.2.2), the user agent must run the above steps as if stop had been called.

I agree. Both the `RTCPeerConnection.close` and "set an `RTCSessionDescription`" sections should just reference the `RTCRtpTransceiver.stop` steps directly, where applicable.

GitHub Notification of comment by taylor-b
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1575#issuecomment-327922351 using your GitHub account
Received on Thursday, 7 September 2017 20:44:23 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:42 UTC