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.
| Bubbles | No |
|---|---|
| Cancelable | No |
| Interface | MediaStreamEvent |
| Event handler property | RTCPeerConnection.onremovestream |
Warning: This 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, which caused a removestream event.
Browser compatibility
| Desktop | Mobile | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Chrome | Edge | Firefox | Internet Explorer | Opera | Safari | WebView Android | Chrome Android | Firefox for Android | Opera Android | Safari on IOS | Samsung Internet | |
removestream_event |
24
See bug 697059.
|
15 |
22-60 |
No |
15 |
No |
≤37 |
25
See bug 697059.
|
44-60 |
14 |
No |
1.5 |
See also
© 2005–2021 MDN contributors.
Licensed under the Creative Commons Attribution-ShareAlike License v2.5 or later.
https://developer.mozilla.org/en-US/docs/Web/API/RTCPeerConnection/removestream_event