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.

Sign up for GitHub

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

Jump to bottom

Receiver.stop() does it emit ontrackended event? #596

Closed
robin-raymond opened this issue Sep 9, 2016 · 1 comment
Closed

Receiver.stop() does it emit ontrackended event? #596

robin-raymond opened this issue Sep 9, 2016 · 1 comment
Assignees
@aboba
Labels
1.0 compatibility issue PR exists

Comments

@robin-raymond
Copy link
Contributor

I think it needs to...
@aboba aboba mentioned this issue Sep 28, 2016
Closed
@aboba
Copy link
Contributor

aboba commented Oct 25, 2016

@robin-raymond Discussion in WEBRTC WG indicates that transceiver.stop() automatically ends transceiver.receiver.track, so that no "onended" Event is fired. See WebRTC Issue w3c/webrtc-pc#878

aboba added a commit that referenced this issue Oct 25, 2016
@aboba
Receiver.stop() does not cause receiver.track onended event
903c9aa 
Fix for Issue #596

Related WebRTC Issue: w3c/webrtc-pc#878
@aboba aboba mentioned this issue Oct 25, 2016
Merged
@aboba aboba self-assigned this Oct 25, 2016
@aboba aboba closed this as completed Oct 26, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@aboba aboba

Labels
1.0 compatibility issue PR exists
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@aboba @robin-raymond