This is an experimental technology
Because this technology's specification has not stabilized, check the compatibility table for usage in various browsers. Also note that the syntax and behavior of an experimental technology is subject to change in future versions of browsers as the specification changes.
The RTCPeerConnection.onaddstream event handler is a property containing the code to execute when the addstream event, of type MediaStreamEvent, is received by this RTCPeerConnection. Such an event is sent when a MediaStream is added to this connection by the remote peer. The event is sent immediately after the call RTCPeerConnection.setRemoteDescription() and doesn't wait for the result of the SDP negotiation.
Syntax
peerconnection.onaddstream = function;
Values
functionis 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.onaddstream = function(ev) { alert("onaddstream event detected!"); };
Specifications
| Specification | Status | Comment |
|---|---|---|
| WebRTC 1.0: Real-time Communication Between Browser The definition of 'RTCPeerConnection.onaddstream' in that specification. |
Working Draft | Initial specification. |
Browser compatibility
| Feature | Chrome | Firefox (Gecko) | Internet Explorer | Opera | Safari |
|---|---|---|---|---|---|
| Basic support | (Yes) [1] | (Yes) [1] | Not supported | (Yes) | ? |
| Feature | Android | Chrome for Android | Firefox Mobile (Gecko) | IE Mobile | Opera Mobile | Safari Mobile |
|---|---|---|---|---|---|---|
| Basic support | ? | ? | ? | Not supported | ? | ? |
[1] Though this property is not prefixed, the interface it belongs to is.
See also
- The
addstreamevent and its type,MediaStreamEvent.