Deprecated
This feature has been removed from the Web standards. Though some browsers may still support it, it is in the process of being dropped. 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.
This is an experimental technology
Check the Browser compatibility table carefully before using this in production.
An addstream
event is fired on a RTCPeerConnection
when a new MediaStream
object has been added to it.
This event has been removed from the WebRTC specification in favor of the track
event and the corresponding RTCPeerConnection.ontrack
event handler property.
An event handler for this event can be added using the RTCPeerConnection.onaddstream
property.
General info
- Specification
- WebRTC 1.0: Real-time Communication Between Browsers
The definition of 'addstream' in that specification. - Interface
MediaStreamEvent
- Bubbles
- No
- Cancelable
- No
- Target
RTCPeerConnection
- Default Action
- None
Properties
A MediaStreamEvent
being an Event
, this event also implements these properties.
stream
Read only- Is the
MediaStream
that has been added to the target.
Methods
A MediaStreamEvent
being an Event
, this event also implements these properties. There are no MediaStreamEvent
-specific methods.
Related Events
Specifications
Specification | Status | Comment |
---|---|---|
WebRTC 1.0: Real-time Communication Between Browsers The definition of 'addstream' in that specification. |
Working Draft | Initial definition. |
Browser compatibility
Feature | Chrome | Edge | Firefox (Gecko) | Internet Explorer | Opera | Safari |
---|---|---|---|---|---|---|
Basic support | (Yes) | (Yes) | 22 (22) Removed in Firefox 46 |
No support | (Yes) | ? |
Feature | Android | Chrome for Android | Edge | Firefox Mobile (Gecko) | IE Mobile | Opera Mobile | Safari Mobile |
---|---|---|---|---|---|---|---|
Basic support | ? | ? | (Yes) | 22 (22) Removed in Firefox 46 |
No support | ? | ? |