New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

creating an RTPSender with a track whose readyState is 'ended' #278

fippo opened this Issue Nov 17, 2015 · 0 comments


None yet
2 participants
Copy link

fippo commented Nov 17, 2015

When attempting to create an RTPSender with a track whose readyState is 'ended' (e.g. because track.stop() has been called or the user unplugged the webcam) what should happen?

Since that state can't be left (see it does not seem useful to 'send' this track to the remote peer.

This affects two sections in the spec, first the constructor @*
I would propose the following change:
If an attempt is made to construct an RTCRtpSender object with transport.state or rtcpTransport.state "closed" or the track.readyState is "ended", throw an InvalidStateError exception.

Second, the setTrack method @
How about this for the new step 3.2 before the current step 3.2?
If withTrack.readyState is "ended", then reject p with ToBeDefinedMediaStreamTrackError and abort these steps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment