RTCPeerConnection: removestream event - Web APIs 编辑
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 |
Important: 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
BCD tables only load in the browser
See also
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论