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

The steps in `RTCRtpTransceiver.stop` actually seem to say the right thing:

> `receiver.track` is now said to be [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]( 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 using your GitHub account

Received on Thursday, 7 September 2017 15:38:01 UTC