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 15:38:02 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-327838126-1504798672-sysbot+gh@w3.org>
The steps in `RTCRtpTransceiver.stop` actually seem to say the right thing:

> `receiver.track` is now said to be [ended](https://www.w3.org/TR/mediacapture-streams/#track-ended).

Which links to the steps for changing `readyState` in the mediacapture spec, which you quoted. Below it also explicitly says:

> the steps described in [track ended](https://www.w3.org/TR/mediacapture-streams/#track-ended) must be followed.

So, I think all these issues would be fixed if the `RTCPeerConnection.close` algorithm referenced the `RTCRtpTransceiver.stop` algorithm instead of duplicating the steps. Which I believe has been suggested in another issue.

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

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