RTCPeerConnection: removestream event
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.
The obsolete removestream
event was sent to an RTCPeerConnection
to inform it that a MediaStream
had been removed from the connection.
You can use the RTCPeerConnection
interface's onremovestream
property to set a handler for this event.
This is the counterpart to the addstream
event, which is also obsolete.
Warning: This event has been removed from the WebRTC specification in favor of the existing removetrack
event on the remote MediaStream
and the corresponding 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, which caused a removestream
event.
This event is not cancelable and does not bubble.
Syntax
Use the event name in methods like addEventListener()
, or set an event handler property.
addEventListener('removestream', event => { });
onremovestream = event => { };
Event type
An MediaStreamEvent
. Inherits from Event
.
Event properties
A MediaStreamEvent
being an Event
, this event also implements these properties.
MediaStreamEvent.stream
Read only-
Contains the
MediaStream
containing the stream associated with the event.
Browser compatibility
BCD tables only load in the browser