Deprecated
This feature is no longer recommended. Though some browsers might still support it, it may have already been removed from the relevant web standards, may be in the process of being dropped, or may only be kept for compatibility purposes. Avoid using it, and update existing code if possible; see the compatibility table at the bottom of this page to guide your decision. Be aware that this feature may cease to work at any time.
Experimental
This is an experimental technology
Check the Browser compatibility table carefully before using this in production.
The removestream
event has been removed from the WebRTC specification in favor of the existing removetrack
event on the remote MediaStream
and the corresponding MediaStream.onremovetrack
event handler property of the remote MediaStream
. The RTCPeerConnection
API is now track-based, so having zero tracks in the remote stream is equivalent to the remote stream being removed and the old removestream event.
The RTCPeerConnection.onremovestream
event handler is a property containing the code to execute when the removestream
event, of type MediaStreamEvent
, is received by this RTCPeerConnection
. Such an event is sent when a MediaStream
is removed from this connection.
Syntax
peerconnection.onremovestream = function;
Values
function
is the name of a user-defined function, without the()
suffix or any parameters, or an anonymous function declaration, such asfunction(event) {...}
. An event handler always has one single parameter, containing the event, here of typeMediaStreamEvent
.
Example
pc.onremovestream = function(ev) { alert("onremovestream event detected!"); };
Browser compatibility
BCD tables only load in the browser
See also
- The
removestream
event and its type,MediaStreamEvent
.