Skip to content
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

null Track in RtpSender #656

Closed
aboba opened this issue Feb 7, 2017 · 1 comment
Closed

null Track in RtpSender #656

aboba opened this issue Feb 7, 2017 · 1 comment

Comments

@aboba
Copy link
Contributor

@aboba aboba commented Feb 7, 2017

In WebRTC 1.0, replaceTrack(null) is permitted, and also, an RtpSender can be constructed with a null track. So ORTC needs to be compatible with this.

@fippo
Copy link
Contributor

@fippo fippo commented Feb 7, 2017

if no track is provided a kind is probably required -- that probably implies a constructor that takes a trackOrKind similar to the 1.0 createTransceiver.

aboba added a commit that referenced this issue Feb 13, 2017
@aboba aboba self-assigned this Feb 13, 2017
@aboba aboba added the PR exists label Feb 13, 2017
@aboba aboba closed this Feb 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants