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?
to your account
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.
The text was updated successfully, but these errors were encountered:
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.
null Track in RtpSender
Fix for Issue #656
Successfully merging a pull request may close this issue.