我们的志愿者还没有将这篇文章翻译为 中文 (简体)。加入我们帮助完成翻译！
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.
A datachannel event informs the target, a RTCPeerConnection object, that a RTCDataChannel has been added to the connection, as a result of a call to RTCPeerConnection.createDataChannel() by the remote peer.
This event is not dispatched when the local end of the connection creates the channel.
An event handler for this event can be added via the RTCPeerConnection.ondatachannel property.
General info
- Specification
- WebRTC 1.0: Real-time Communication Between Browser
The definition of 'datachannel' in that specification. - Interface
RTCDataChannelEvent- Bubbles
- No
- Cancelable
- No
- Target
RTCPeerConnection- Default Action
- None
Properties
RTCDataChannelEvent is based on Event, so it also implements its properties.
channelRead only- A
RTCDataChannelwhich represents the data channel which was added to theRTCPeerConnection.
Methods
RTCDataChannelEvent is based on Event, so it also implements its properties. There are no methods specific to RTCDataChannelEvent.
Related Events
- none
Specifications
| Specification | Status | Comment |
|---|---|---|
| WebRTC 1.0: Real-time Communication Between Browser The definition of 'datachannel' in that specification. |
Working Draft | Basic definition. |
Browser compatibility
| Feature | Chrome | Firefox (Gecko) | Internet Explorer | Opera | Safari |
|---|---|---|---|---|---|
| Basic support | (Yes) | 22 (22) | No support | (Yes) | ? |
| Feature | Android | Chrome for Android | Firefox Mobile (Gecko) | IE Mobile | Opera Mobile | Safari Mobile | Chrome for Android |
|---|---|---|---|---|---|---|---|
| Basic support | No support | 28 [2] | 22.0 (22) | No support | No support | No support | (Yes) |
[2] WebRTC, including RTCDataChannel, was introduced in Chrome 28 for Android behind a flag, and enabled by default starting in Chrome 29 for Android.