RTCPeerConnection: addstream event - Web APIs 编辑
Obsolete
This feature is obsolete. Although it may still work in some browsers, its use is discouraged since it could be removed at any time. Try to avoid using it.
The obsolete addstream
event is sent to an RTCPeerConnection
when new media, in the form of a MediaStream
object, has been added to it.
Important: This event has been removed from the WebRTC specification. You should instead watch for the track
event, which is sent for each media track added to the RTCPeerConnection
.
Bubbles | No |
---|---|
Cancelable | No |
Interface | MediaStreamEvent |
Event handler property | RTCPeerconnection.onaddstream |
You can, similarly, watch for streams to be removed from the connection by monitoring the removestream
event.
Examples
This example looks to determine if the user's browser supports the track
event. If it does, a track
event listener is set up; otherwise, an addstream
event listener is set up. pc
is an RTCPeerConnection
.
if (pc.addTrack !== undefined) {
pc.ontrack = ev => {
ev.streams.forEach(stream => doAddStream(stream));
}
} else {
pc.onaddstream = ev => {
doAddStream(ev.stream);
}
}
This calls a function doAddStream()
once for each stream being added to the RTCPeerConnection
, regardless of whether the browser sends addstream
or track
.
You can also use the addEventListener()
method to set an event listener:
pc.addEventListener("addstream", ev => doAddStream(ev.stream), false);
Browser compatibility
BCD tables only load in the browser
See also
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论