Jan-Ivar Bruaroey [:jib] (needinfo? me) Reporter
	Description • 8 years ago

The arrival of transceivers in the spec affects the behavior of our already implemented pc.removeTrack, which in the spec was subsequently changed [2] to no longer remove the sender from getSenders().

May not make sense to fix until we add transceivers (Bug 1290948).

[1] https://github.com/w3c/webrtc-pc/commit/67f7c4108c40434fc4e9bfbf77b7d909a39b4db3#diff-25266486aad3fa9244c53420694e037eL2519

	Bulk Bug Changes for mreavy's org
	Comment 1 • 7 years ago

Mass change P2->P3 to align with new Mozilla triage process.

	Byron Campen [:bwc] Assignee
	Comment 2 • 7 years ago

This is probably fixed in bug 1290948, but we should probably have a removeTrack test in test_peerConnection_transceivers.html.

	Jan-Ivar Bruaroey [:jib] (needinfo? me) Reporter
	Comment 4 • 6 years ago
mozreview-review

Comment on attachment 8951730 [details]
Bug 1290949: Test that removeTrack does not remove the associated sender.

https://reviewboard.mozilla.org/r/221008/#review227498

	Pulsebot
	Comment 5 • 6 years ago

Pushed by bcampen@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/3ae40dfba516
Test that removeTrack does not remove the associated sender. r=jib

	Stefan Hindli [:stefan_hindli]
	Comment 6 • 6 years ago
bugherder

https://hg.mozilla.org/mozilla-central/rev/3ae40dfba516

	Eric Shepherd [:sheppy]
	Comment 7 • 6 years ago

Updated https://developer.mozilla.org/en-US/docs/Web/API/RTCPeerConnection/removeTrack and Firefox 60 for developers to note this change.