この記事は翻訳作業中です。

RTCPeerConnection インターフェイスはローカルコンピューターとリモートピア間の WebRTC コネクションを表現します。このインターフェイスはリモートピアへ接続や、その接続の保守や監視するメソッド、さらに、不要になった接続を閉じるメソッドを提供します。

コンストラクター

RTCPeerConnection()
RTCPeerConnection() コンストラクターはRTCPeerConnectionを新たに作成し、返します。これは、ローカルデバイスとリモートピアの間の接続を表現します。

プロパティ

Also inherits プロパティ from: EventTarget

canTrickleIceCandidates [翻訳する]
The read-only RTCPeerConnection property canTrickleIceCandidates returns a Boolean which indicates whether or not the remote peer can accept trickled ICE candidates.
connectionState [翻訳する]
The read-only connectionState property of the RTCPeerConnection interface indicates the current state of the peer connection by returning one of the string values specified by the enum RTCPeerConnectionState.
currentLocalDescription 読取専用 [翻訳する]
The read-only property RTCPeerConnection.currentLocalDescription returns an RTCSessionDescription object describing the local end of the connection as it was most recently successfully negotiated since the last time the  RTCPeerConnection finished negotiating and connecting to a remote peer. Also included is a list of any ICE candidates that may already have been generated by the ICE agent since the offer or answer represented by the description was first instantiated.
currentRemoteDescription 読取専用 [翻訳する]
The read-only property RTCPeerConnection.currentRemoteDescription returns an RTCSessionDescription object describing the remote end of the connection as it was most recently successfully negotiated since the last time the RTCPeerConnection finished negotiating and connecting to a remote peer. Also included is a list of any ICE candidates that may already have been generated by the ICE agent since the offer or answer represented by the description was first instantiated.
defaultIceServers [翻訳する]
The read-only property RTCPeerConnection.defaultIceServers returns an array of objects based on the RTCIceServer dictionary, which indicates what, if any, ICE servers the browser will use by default if none are provided to the RTCPeerConnection in its RTCConfiguration. However, browsers are not required to provide any default ICE servers at all.
iceConnectionState 読取専用 [翻訳する]
The read-only property RTCPeerConnection.iceConnectionState returns an enum of type RTCIceConnectionState which state of the ICE agent associated with the RTCPeerConnection.
iceGatheringState 読取専用 [翻訳する]
The read-only property RTCPeerConnection.iceGatheringState returns an enum of type RTCIceGatheringState that describes connection's ICE gathering state. This lets you detect, for example, when collection of ICE candidates has finished.
localDescription 読取専用 [翻訳する]
The read-only property RTCPeerConnection.localDescription returns an RTCSessionDescription describing the session for the local end of the connection. If it has not yet been set, this is null.
peerIdentity 読取専用 [翻訳する]
The read-only RTCPeerConnection property peerIdentity returns a JavaScript Promise that resolves to an RTCIdentityAssertion which contains a DOMString identifying the remote peer.
pendingLocalDescription 読取専用 [翻訳する]
The read-only property RTCPeerConnection.pendingLocalDescription returns an RTCSessionDescription object describing a pending configuration change for the local end of the connection. This does not describe the connection as it currently stands, but as it may exist in the near future. Use RTCPeerConnection.currentLocalDescription or RTCPeerConnection.localDescription to get the current state of the endpoint. For details on the difference, see Pending and current descriptions in WebRTC connectivity.
pendingRemoteDescription 読取専用 [翻訳する]
The read-only property RTCPeerConnection.pendingRemoteDescription returns an RTCSessionDescription object describing a pending configuration change for the remote end of the connection. This does not describe the connection as it currently stands, but as it may exist in the near future. Use RTCPeerConnection.currentRemoteDescription or RTCPeerConnection.remoteDescription to get the current session description for the remote endpoint. For details on the difference, see Pending and current descriptions in WebRTC connectivity.
remoteDescription 読取専用 [翻訳する]
The read-only property RTCPeerConnection.remoteDescription returns a RTCSessionDescription describing the session (which includes configuration and media information) for the remote end of the connection. If this hasn't been set yet, this is null.
sctp [翻訳する]
The read-only sctp property on the RTCPeerConnection interface returns an RTCSctpTransport describing the SCTP transport over which SCTP data is being sent and received. If SCTP hasn't been negotiated, this value is null.
signalingState 読取専用 [翻訳する]
The read-only signalingState property on the RTCPeerConnection interface returns one of the string values specified by the RTCSignalingState enum; these values describe the state of the signaling process on the local end of the connection while connecting or reconnecting to another peer. See Signaling in Lifetime of a WebRTC session for more details about the signaling process.

イベントハンドラー

Also inherits イベントハンドラー from: EventTarget

onaddstream [翻訳する]
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 setRemoteDescription() and doesn't wait for the result of the SDP negotiation.
onconnectionstatechange [翻訳する]
The RTCPeerConnection.onconnectionstatechange property specifies an EventHandler which is called to handle the connectionstatechange event when it occurs on an instance of RTCPeerConnection. This happens whenever the aggregate state of the connection changes.
ondatachannel [翻訳する]
The RTCPeerConnection.ondatachannel property is an EventHandler which specifies a function which is called when the datachannel event occurs on an RTCPeerConnection. This event, of type RTCDataChannelEvent, is sent when an RTCDataChannel is added to the connection by the remote peer calling createDataChannel().
onicecandidate [翻訳する]
The RTCPeerConnection.onicecandidate property is an EventHandler which specifies a function to be called when the icecandidate event occurs on an RTCPeerConnection instance. This happens whenever the local ICE agent needs to deliver a message to the other peer through the signaling server.
oniceconnectionstatechange [翻訳する]
The RTCPeerConnection.oniceconnectionstatechange property is an event handler which specifies a function to be called when the iceconnectionstatechange event is fired on an RTCPeerConnection instance. This happens when the state of the connection's ICE agent, as represented by the iceConnectionState property, changes.
onicegatheringstatechange [翻訳する]
The RTCPeerConnection.onicegatheringstatechange property is an EventHandler which specifies a function to be called when the icegatheringstatechange event is sent to an RTCPeerConnection instance. This happens when the ICE gathering state—that is, whether or not the ICE agent is actively gathering candidates—changes.
onidentityresult [翻訳する]
The RTCPeerConnection.onidentityresult event handler is a property containing the code to execute when the identityresult event, of type RTCIdentityEvent, is received by this RTCPeerConnection. Such an event is sent when an identity assertion is generated, via getIdentityAssertion() or during the creation of an offer or an answer.
onidpassertionerror [翻訳する]
The RTCPeerConnection.onidpassertionerror event handler is a property containing the code to execute whent the idpassertionerror event, of type RTCIdentityErrorEvent, is received by this RTCPeerConnection. Such an event is sent when the associated identity provider (IdP) encounters an error while generating an identity assertion.
onidpvalidationerror [翻訳する]
The RTCPeerConnection.onidpvalidationerror event handler is a property containing the code to execute whent the idpvalidationerror event, of type RTCIdentityErrorEvent, is received by this RTCPeerConnection. Such an event is sent when the associated identity provider (IdP) encounters an error while validating an identity assertion.
onnegotiationneeded [翻訳する]
The RTCPeerConnection.onnegotiationneeded property is an EventHandler which specifies a function which is called to handle the negotiationneeded event when it occurs on an RTCPeerConnection instance. This event is fired when a change has occurred which requires session negotiation. This negotiation should be carried out as the offerer, because some session changes cannot be negotiated as the answerer.
onpeeridentity [翻訳する]
The RTCPeerConnection.onpeeridentity event handler is a property containing the code to execute whent the peeridentity event, of type Event, is received by this RTCPeerConnection. Such an event is sent when an identity assertion, received from a peer, has been successfully validated.
onremovestream [翻訳する]
The RTCPeerConnection.onremovestream event handler is a property containing the code to execute when the removestream event, of type MediaStreamEvent, is received by this RTCPeerConnection. Such an event is sent when a MediaStream is removed from this connection.
onsignalingstatechange [翻訳する]
The onsignalingstatechange property of the RTCPeerConnection interface is an EventHandler which specifies a function to be called when the signalingstatechange event occurs on an RTCPeerConnection interface.
ontrack [翻訳する]
The RTCPeerConnection property ontrack is an EventHandler which specifies a function to be called when the track event occurs, indicating that a track has been added to the RTCPeerConnection.

メソッド

Also inherits メソッド from: EventTarget

addIceCandidate() [翻訳する]
When a web site or app using RTCPeerConnection receives a new ICE candidate from the remote peer over its signaling channel, it delivers the newly-received candidate to the browser's ICE agent by calling RTCPeerConnection.addIceCandidate().
addStream() [翻訳する]
The obsolete RTCPeerConnection method addStream() adds a MediaStream as a local source of audio or video. Instead of using this obsolete method, you should instead use addTrack() once for each track you wish to send to the remote peer.
addTrack() [翻訳する]
The RTCPeerConnection method addTrack() adds a new media track to the set of tracks which will be transmitted to the other peer.
close() [翻訳する]
The RTCPeerConnection.close() method closes the current peer connection.
createAnswer() [翻訳する]
The createAnswer() method on the RTCPeerConnection interface creates an SDP answer to an offer received from a remote peer during the offer/answer negotiation of a WebRTC connection. The answer contains information about any media already attached to the session, codecs and options supported by the browser, and any ICE candidates already gathered. The answer is delivered to the returned Promise, and should then be sent to the source of the offer to continue the negotiation process.
createDataChannel() [翻訳する]
The createDataChannel() method on the RTCPeerConnection interface creates a new channel over which any kind of data may be transmitted. This can be useful for back-channel content such as images, file transfer, text chat, game update packets, and so forth.
createOffer() [翻訳する]
The createOffer() method of the RTCPeerConnection interface initiates the creation of an SDP offer for the purpose of starting a new WebRTC connection to a remote peer.
generateCertificate() [翻訳する]
The generateCertificate() method of the RTCPeerConnection interface creates and stores an X.509 certificate and corresponding private key then returns an RTCCertificate, providing access to it.
getConfiguration() [翻訳する]
The RTCPeerConnection.getConfiguration() method returns an RTCConfiguration object which indicates the current configuration of the RTCPeerConnection on which the method is called.
getIdentityAssertion() [翻訳する]
The RTCPeerConnection.getIdentityAssertion() method initiates the gathering of an identity assertion. This has an effect only if the signalingState is not "closed".
getLocalStreams() [翻訳する]
The RTCPeerConnection.getLocalStreams() method returns an array of MediaStream associated with the local end of the connection. The array may be empty.
getReceivers() [翻訳する]
The RTCPeerConnection.getReceivers() method returns an array of RTCRtpReceiver objects, each of which represents one RTP receiver. Each RTP receiver manages the reception and decoding of data for a MediaStreamTrack on an RTCPeerConnection
getRemoteStreams() [翻訳する]
The RTCPeerConnection.getRemoteStreams() method returns an array of MediaStream associated with the remote end of the connection. The array may be empty.
getSenders() [翻訳する]
The RTCPeerConnection method getSenders() returns an array of RTCRtpSender objects, each of which represents the RTP sender responsible for transmitting one track's data.
getStats() [翻訳する]
The RTCPeerConnection method getStats() returns a promise which resolves with data providing statistics about either the overall connection or about the specified MediaStreamTrack.
getStreamById() [翻訳する]
The RTCPeerConnection.getStreamById() method returns the MediaStream with the given id that is associated with local or remote end of the connection. If no stream matches, it returns null.
removeStream() [翻訳する]
The RTCPeerConnection.removeStream() method removes a MediaStream as a local source of audio or video. If the negotiation already happened, a new one will be needed for the remote peer to be able to use it. Because this method has been deprecated, you should instead use removeTrack() if your target browser versions have implemented it.
removeTrack() [翻訳する]
The RTCPeerConnection.removeTrack() method tells the local end of the connection to stop sending media from the specified track, without actually removing the corresponding RTCRtpSender from the list of senders as reported by RTCPeerConnection.getSenders().
setConfiguration() [翻訳する]
The RTCPeerConnection.setConfiguration() method sets the current configuration of the RTCPeerConnection based on the values included in the specified RTCConfiguration object. This lets you change the ICE servers used by the connection and which transport policies to use.
setIdentityProvider() [翻訳する]
The RTCPeerConnection.setIdentityProvider() method sets the Identity Provider (IdP) to the triplet given in parameter: its name, the protocol used to communicate with it (optional) and an optional username. The IdP will be used only when an assertion is needed.
setLocalDescription() [翻訳する]
The RTCPeerConnection.setLocalDescription() method changes the local description associated with the connection. This description specifies the properties of the local end of the connection, including the media format.
setRemoteDescription() [翻訳する]
The RTCPeerConnection.setRemoteDescription() method changes the remote description associated with the connection. This description specifies the properties of the remote end of the connection, including the media format.

廃止されたメソッド

以下のメソッドは廃止されており、すべての主要なブラウザーで未実装です。

RTCPeerConnection.createDTMFSender()
特定の MediaStreamTrack と関連付けられた新たな RTCDTMFSender を生成します。これにより、その接続において DTMF 音(電話のトーン信号、プッシュ音)を送れるようになるでしょう。

イベント

Listen to these events using addEventListener() or by assigning an event listener to the oneventname property of this interface.

connectionstatechange
Sent to the RTCPeerConnection object when the overall connectivity status of the RTCPeerConnection changes.
Also available through the onconnectionstatechange event handler property.
datachannel
Sent to the RTCPeerConnection object when the remote peer adds an RTCDataChannel to the connection.
Also available through the ondatachannel event handler property.
icecandidate
Sent to the object when a new ICE candidate arrives during negotiation.
Also available using the onicecandidate event handler property.
iceconnectionstatechange
Sent to the RTCPeerConnection when the state of the ICE connection changes, such as when it disconnects.
Also available using the oniceconnectionstatechange event handler property.
negotiationneeded
Sent to the RTCPeerConnection when it's time to perform ICE negotiation. This can happen both when first opening a connection as well as any time it's necessary to adapt to changing network conditions.
Also available using the onnegotiationneeded event handler property.
icecandidate
Sent to the peer connection to request that the specified candidate be transmitted to the remote peer.
Also available through the onicecandidate event handler property.
negotiationneeded
Sent to the RTCPeerConnection when negotiation or renegotiation of the ICE connection needs to be performed. The receiver should respond by creating an offer and sending it to the other peer.
Also available as the onnegotiationneeded event handler property.
signalingstatechange
The signalingstatechange event is sent to the RTCPeerConnection when the connection's ICE signaling state changes.
Also available through the onsignalingstatechange event handler property.
track
The track event is sent after a new track has been added to one of the RTCRtpReceiver instances which comprise the connection.
Available as the ontrack event handler property.

Obsolete events

addstream
Sent when a new MediaStream has been added to the connection. Instead of watching for this obsolete event, you should watch each for track events; one is sent for each MediaStreamTrack added to the connection.
Available as the onaddstream event handler property.
identityresult
In old versions of the WebRTC specification, this event was used to indicate that an identity assertion is available. Now, you should instead wait for a the promise returned by peerIdentity to resolve with an identity.
Also available using the onidentityresult event handler property.
idpassertionerror
In old versions of the WebRTC specification, this event was used to indicate that an error occurred while attempting to generate an identity assertion. Now, you should instead wait for a the promise returned by peerIdentity to be rejected with an error.
Also available as the onidpinsertionerror event handler property.
idpvalidationerror
In old versions of the WebRTC specification, this event was used to indicate that an error occurred while attempting to validate an identity assertion. Now, you should instead wait for a the promise returned by peerIdentity to be rejected with an error.
Also available using the onpeerdentity event handler property.
peeridentity
In old versions of the WebRTC specification, this event was used to deliver a received identity. Now, you should instead wait for a the promise returned by peerIdentity to resolve with an identity.
removestream
Sent to the RTCPeerConnection when a MediaStream is removed from the connection. Instead of watching for this obsolete event, you should watch each stream for removetrack events on each stream within the RTCPeerConnection.
Also available as the onaddstream event handler property.

定数

RTCBundlePolicy enum

この RTCBundlePolicy 列挙型は、リモートピアが、単一の転送リンクにおいて複数のメディアストリームをまとめるための SDP BUNDLE standard と互換していない場合に、ICEの候補を収集するために特定のポリシーを要求する時に使用される文字列定数を定義します。

Note: In technical terms, a BUNDLE lets all media flow between two peers flow across a single 5-tuple; that is, from the same IP and port on one peer to the same IP and port on the other peer, using the same transport protocol.

Constant Description
"balanced" On BUNDLE-aware connections, the ICE agent should gather candidates for all of the media types in use (audio, video, and data). Otherwise, the ICE agent should only negotiate one audio and video track on separate transports.
"max-compat" The ICE agent should gather candidates for each track, using separate transports to negotiate all media tracks for connections which aren't BUNDLE-compatible.
"max-bundle" The ICE agent should gather candidates for just one track. If the connection isn't BUNDLE-compatible, then the ICE agent should negotiate just one media track.

RTCIceConnectionState enum

The RTCIceConnectionState enum defines the string constants used to describe the current state of the ICE agent and its connection to the ICE server (that is, the STUN or TURN server).

Constant Description
"new" The ICE agent is gathering addresses or is waiting to be given remote candidates through calls to RTCPeerConnection.addIceCandidate() (or both).
"checking" The ICE agent has been given one or more remote candidates and is checking pairs of local and remote candidates against one another to try to find a compatible match, but has not yet found a pair which will allow the peer connection to be made. It's possible that gathering of candidates is also still underway.
"connected" A usable pairing of local and remote candidates has been found for all components of the connection, and the connection has been established. It's possible that gathering is still underway, and it's also possible that the ICE agent is still checking candidates against one another looking for a better connection to use.
"completed" The ICE agent has finished gathering candidates, has checked all pairs against one another, and has found a connection for all components.
"failed" The ICE candidate has checked all candidates pairs against one another and has failed to find compatible matches for all components of the connection. It is, however, possible that the ICE agent did find compatible connections for some components.
"disconnected" Checks to ensure that components are still connected failed for at least one component of the RTCPeerConnection. This is a less stringent test than "failed" and may trigger intermittently and resolve just as spontaneously on less reliable networks, or during temporary disconnections. When the problem resolves, the connection may return to the "connected" state.
"closed" The ICE agent for this RTCPeerConnection has shut down and is no longer handling requests.

RTCIceGatheringState enum

The RTCIceGatheringState enum defines string constants which reflect the current status of ICE gathering, as returned using the RTCPeerConnection.iceGatheringState property. You can detect when this value changes by watching for an event of type icegatheringstatechange.

Constant Description
"new" The peer connection was just created and hasn't done any networking yet.
"gathering" The ICE agent is in the process of gathering candidates for the connection.
"complete" The ICE agent has finished gathering candidates. If something happens that requires collecting new candidates, such as a new interface being added or the addition of a new ICE server, the state will revert to "gathering" to gather those candidates.

RTCIceTransportPolicy enum

The RTCIceTransportPolicy enum defines string constants which can be used to limit the transport policies of the ICE candidates to be considered during the connection process.

Constant Description
"all" All ICE candidates will be considered.
"public" Only ICE candidates with public IP addresses will be considered. Removed from the specification's May 13, 2016 working draft.
"relay" Only ICE candidates whose IP addresses are being relayed, such as those being passed through a TURN server, will be considered.

RTCPeerConnectionState enum

The RTCPeerConnectionState enum defines string constants which describe states in which the RTCPeerConnection may be. These values are returned by the connectionState property. This state essentially represents the aggregate state of all ICE transports (which are of type RTCIceTransport or RTCDtlsTransport) being used by the connection.

Constant Description
"new" At least one of the connection's ICE transports (RTCIceTransports or RTCDtlsTransports) are in the "new" state, and none of them are in one of the following states: "connecting", "checking", "failed", or "disconnected", or all of the connection's transports are in the "closed" state.
"connecting" One or more of the ICE transports are currently in the process of establishing a connection; that is, their RTCIceConnectionState is either "checking" or "connected", and no transports are in the "failed" state. <<< Make this a link once I know where that will be documented
"connected" Every ICE transport used by the connection is either in use (state "connected" or "completed") or is closed (state "closed"); in addition, at least one transport is either "connected" or "completed".
"disconnected" At least one of the ICE transports for the connection is in the "disconnected" state and none of the other transports are in the state "failed", "connecting", or "checking".
"failed" One or more of the ICE transports on the connection is in the "failed" state.
"closed"

The RTCPeerConnection is closed.

This value was in the RTCSignalingState enum (and therefore found by reading the value of the signalingState) property until the May 13, 2016 draft of the specification.

RTCRtcpMuxPolicy enum

The RTCRtcpMuxPolicy enum defines string constants which specify what ICE candidates are gathered to support non-multiplexed RTCP. <<<add a link to info about multiplexed RTCP.

Constant Description
"negotiate" Instructs the ICE agent to gather both RTP and RTCP candidates. If the remote peer can multiplex RTCP, then RTCP candidates are multiplexed atop the corresponding RTP candidates. Otherwise, both the RTP and RTCP candidates are returned, separately.
"require" Tells the ICE agent to gather ICE candidates for only RTP, and to multiplex RTCP atop them. If the remote peer doesn't support RTCP multiplexing, then session negotiation fails.

RTCSignalingState enum

The RTCSignalingState enum specifies the possible values of RTCPeerConnection.signalingState, which indicates where in the process of signaling the exchange of offer and answer the connection currently is.

Constant Description
"stable" There is no ongoing exchange of offer and answer underway. This may mean that the RTCPeerConnection object is new, in which case both the localDescription and remoteDescription are null; it may also mean that negotiation is complete and a connection has been established.
"have-local-offer" The local peer has called RTCPeerConnection.setLocalDescription(), passing in SDP representing an offer (usually created by calling RTCPeerConnection.createOffer()), and the offer has been applied successfully.
"have-remote-offer" The remote peer has created an offer and used the signaling server to deliver it to the local peer, which has set the offer as the remote description by calling RTCPeerConnection.setRemoteDescription().
"have-local-pranswer" The offer sent by the remote peer has been applied and an answer has been created (usually by calling RTCPeerConnection.createAnswer()) and applied by calling RTCPeerConnection.setLocalDescription(). This provisional answer describes the supported media formats and so forth, but may not have a complete set of ICE candidates included. Further candidates will be delivered separately later.
"have-remote-pranswer" A provisional answer has been received and successfully applied in response to an offer previously sent and established by calling setLocalDescription().
"closed"

The connection is closed.

Note: This value moved into the RTCPeerConnectionState enum in the May 13, 2016 draft of the specification, as it reflects the state of the RTCPeerConnection, not the signaling connection. You now detect a closed connection by checking for connectionState to be "closed" instead.

仕様書

仕様書 状態 備考
WebRTC 1.0: Real-time Communication Between Browsers
RTCPeerConnection の定義
勧告候補 初回定義

ブラウザーの対応

Update compatibility data on GitHub
デスクトップモバイル
ChromeEdgeFirefoxInternet ExplorerOperaSafariAndroid webviewAndroid 版 ChromeEdge MobileAndroid 版 FirefoxAndroid 版 OperaiOSのSafariSamsung Internet
RTCPeerConnectionChrome 完全対応 23Edge 完全対応 ありFirefox 完全対応 22IE ? Opera 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari ? WebView Android 完全対応 ありChrome Android 完全対応 25Edge Mobile 完全対応 ありFirefox Android 完全対応 44
完全対応 44
未対応 22 — 44
接頭辞付き
接頭辞付き moz のベンダー接頭辞が必要
Opera Android 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari iOS ? Samsung Internet Android 完全対応 6.0
完全対応 6.0
未対応 5.0 — 6.0
接頭辞付き
接頭辞付き webkit のベンダー接頭辞が必要
RTCPeerConnection()Chrome 完全対応 23
補足
完全対応 23
補足
補足 Before Chrome 63 the default value for the RTCConfiguration.rtcpMuxPolicy parameter was "negotiate"
Edge 完全対応 ありFirefox 完全対応 22IE ? Opera 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari ? WebView Android 完全対応 あり
補足
完全対応 あり
補足
補足 Before Chrome 63 the default value for the RTCConfiguration.rtcpMuxPolicy parameter was "negotiate"
Chrome Android 完全対応 あり
補足
完全対応 あり
補足
補足 Before Chrome 63 the default value for the RTCConfiguration.rtcpMuxPolicy parameter was "negotiate"
Edge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari iOS ? Samsung Internet Android 完全対応 6.0
addIceCandidateChrome 完全対応 51
補足
完全対応 51
補足
補足 Promise-based version.
完全対応 24
Edge 完全対応 15Firefox 完全対応 22IE ? Opera 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari 完全対応 11WebView Android 完全対応 51
補足
完全対応 51
補足
補足 Promise-based version.
完全対応 あり
Chrome Android 完全対応 51
補足
完全対応 51
補足
補足 Promise-based version.
完全対応 あり
Edge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari iOS ? Samsung Internet Android 完全対応 6.0
補足
完全対応 6.0
補足
補足 Promise-based version and unprefixed.
未対応 5.0 — 6.0
補足
補足 Promise-based version.
addStream
非推奨
Chrome 完全対応 24Edge 完全対応 15Firefox 完全対応 22IE ? Opera 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari ? WebView Android 完全対応 ありChrome Android 完全対応 ありEdge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari iOS ? Samsung Internet Android 完全対応 6.0
addstream event
非推奨
Chrome 完全対応 24Edge 完全対応 15Firefox 完全対応 22IE ? Opera 完全対応 43Safari 未対応 なしWebView Android 完全対応 ありChrome Android 完全対応 25Edge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 完全対応 43Safari iOS ? Samsung Internet Android 完全対応 6.0
addTrackChrome 完全対応 64Edge 完全対応 ありFirefox 完全対応 22IE ? Opera 完全対応 51Safari 完全対応 11WebView Android 完全対応 64Chrome Android 完全対応 64Edge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 完全対応 51Safari iOS ? Samsung Internet Android 完全対応 6.0
addTransceiverChrome 完全対応 69Edge 未対応 なしFirefox 完全対応 59IE 未対応 なしOpera 未対応 なしSafari 完全対応 11WebView Android 完全対応 69Chrome Android 完全対応 69Edge Mobile 未対応 なしFirefox Android 完全対応 59Opera Android 未対応 なしSafari iOS 未対応 なしSamsung Internet Android 未対応 なし
canTrickleIceCandidatesChrome 未対応 なしEdge 完全対応 15Firefox 完全対応 47IE ? Opera 未対応 なしSafari ? WebView Android 未対応 なしChrome Android 未対応 なしEdge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 未対応 なしSafari iOS ? Samsung Internet Android 完全対応 6.0
closeChrome 完全対応 23Edge 完全対応 15Firefox 完全対応 ありIE ? Opera ? Safari 完全対応 11WebView Android 完全対応 ありChrome Android 完全対応 ありEdge Mobile ? Firefox Android ? Opera Android ? Safari iOS ? Samsung Internet Android ?
connectionStateChrome 完全対応 72Edge 未対応 なしFirefox 未対応 なしIE 未対応 なしOpera 未対応 なしSafari 完全対応 11WebView Android 完全対応 72Chrome Android 完全対応 72Edge Mobile 未対応 なしFirefox Android 未対応 なしOpera Android 未対応 なしSafari iOS 未対応 なしSamsung Internet Android 未対応 なし
connectionstatechange eventChrome 完全対応 72Edge 未対応 なしFirefox 未対応 なしIE 未対応 なしOpera 未対応 なしSafari 完全対応 11WebView Android 完全対応 72Chrome Android 完全対応 72Edge Mobile 未対応 なしFirefox Android 未対応 なしOpera Android 未対応 なしSafari iOS 未対応 なしSamsung Internet Android 未対応 なし
createAnswerChrome 完全対応 51
補足
完全対応 51
補足
補足 Promise-based version.
完全対応 24
Edge 完全対応 15Firefox 完全対応 22IE ? Opera 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari 完全対応 11WebView Android 完全対応 51
補足
完全対応 51
補足
補足 Promise-based version.
完全対応 あり
Chrome Android 完全対応 51
補足
完全対応 51
補足
補足 Promise-based version.
完全対応 あり
Edge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari iOS ? Samsung Internet Android 完全対応 6.0
補足
完全対応 6.0
補足
補足 Promise-based version and unprefixed.
未対応 5.0 — 6.0
補足
補足 Promise-based version.
createDTMFSender
非推奨
Chrome 完全対応 27Edge 完全対応 ありFirefox 完全対応 22IE ? Opera 未対応 37 — 43
未対応 37 — 43
完全対応 43
補足
補足 Promise-based version.
Safari ? WebView Android 完全対応 ありChrome Android 完全対応 27Edge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari iOS ? Samsung Internet Android 完全対応 6.0
createDataChannelChrome 完全対応 25Edge 未対応 なしFirefox 完全対応 22IE ? Opera 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari 完全対応 11WebView Android 完全対応 ありChrome Android 完全対応 25Edge Mobile 未対応 なしFirefox Android 完全対応 44Opera Android 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari iOS 完全対応 11Samsung Internet Android 完全対応 6.0
createOfferChrome 完全対応 51
補足
完全対応 51
補足
補足 Promise-based version.
完全対応 24
Edge 完全対応 15Firefox 完全対応 22IE ? Opera 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari 完全対応 11WebView Android 完全対応 51
補足
完全対応 51
補足
補足 Promise-based version.
完全対応 あり
Chrome Android 完全対応 51
補足
完全対応 51
補足
補足 Promise-based version.
完全対応 あり
Edge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari iOS ? Samsung Internet Android 完全対応 6.0
補足
完全対応 6.0
補足
補足 Promise-based version and unprefixed.
未対応 5.0 — 6.0
補足
補足 Promise-based version.
currentLocalDescriptionChrome 完全対応 70Edge 完全対応 ありFirefox 完全対応 22IE ? Opera 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari 完全対応 11WebView Android 完全対応 70Chrome Android 完全対応 70Edge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari iOS ? Samsung Internet Android 完全対応 6.0
currentRemoteDescriptionChrome 完全対応 70Edge 未対応 なしFirefox 完全対応 57IE 未対応 なしOpera 未対応 なしSafari 完全対応 11WebView Android 完全対応 70Chrome Android 完全対応 70Edge Mobile 未対応 なしFirefox Android ? Opera Android 未対応 なしSafari iOS 未対応 なしSamsung Internet Android 未対応 なし
datachannel eventChrome 完全対応 25Edge 完全対応 ありFirefox 完全対応 22IE ? Opera 完全対応 43Safari 完全対応 11WebView Android 完全対応 ありChrome Android 完全対応 25Edge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 完全対応 43Safari iOS ? Samsung Internet Android 完全対応 6.0
defaultIceServersChrome 未対応 なしEdge 完全対応 ありFirefox 完全対応 22IE ? Opera 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari ? WebView Android 未対応 なしChrome Android 未対応 なしEdge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari iOS ? Samsung Internet Android 完全対応 6.0
generateCertificateChrome 完全対応 48Edge 完全対応 ありFirefox 完全対応 22IE ? Opera 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari ? WebView Android 完全対応 48Chrome Android 完全対応 48Edge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari iOS ? Samsung Internet Android 完全対応 6.0
getConfigurationChrome 完全対応 70Edge 完全対応 15Firefox 完全対応 22IE ? Opera 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari 完全対応 11WebView Android 完全対応 70Chrome Android 完全対応 70Edge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari iOS ? Samsung Internet Android 完全対応 6.0
getDefaultIceServersChrome 未対応 なしEdge ? Firefox ? IE ? Opera ? Safari ? WebView Android 未対応 なしChrome Android 未対応 なしEdge Mobile ? Firefox Android ? Opera Android ? Safari iOS ? Samsung Internet Android ?
getIdentityAssertionChrome 未対応 なしEdge 完全対応 ありFirefox 完全対応 22IE ? Opera 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari ? WebView Android 未対応 なしChrome Android 未対応 なしEdge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari iOS ? Samsung Internet Android 完全対応 6.0
getLocalStreamsChrome 完全対応 27Edge 完全対応 15Firefox 完全対応 22IE ? Opera 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari ? WebView Android 完全対応 ありChrome Android 完全対応 27Edge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari iOS ? Samsung Internet Android 完全対応 6.0
getReceiversChrome 完全対応 59Edge 完全対応 ありFirefox 完全対応 22IE ? Opera 完全対応 46Safari 完全対応 11WebView Android 完全対応 59Chrome Android 完全対応 59Edge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 完全対応 46Safari iOS ? Samsung Internet Android 完全対応 6.0
getRemoteStreamsChrome 完全対応 27Edge 完全対応 15Firefox 完全対応 22IE ? Opera 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari ? WebView Android 完全対応 ありChrome Android 完全対応 27Edge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari iOS ? Samsung Internet Android 完全対応 6.0
getSendersChrome 完全対応 64Edge 完全対応 ありFirefox 完全対応 22IE ? Opera 完全対応 51Safari 完全対応 11WebView Android 完全対応 64Chrome Android 完全対応 64Edge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 完全対応 51Safari iOS ? Samsung Internet Android 完全対応 6.0
getStatsChrome 完全対応 58
補足
完全対応 58
補足
補足 Promise resolves with RTCStatsReport.
完全対応 54
補足
補足 Promise-based version.
完全対応 24
Edge 完全対応 15Firefox 完全対応 ありIE ? Opera 完全対応 45Safari 完全対応 11WebView Android 完全対応 58
補足
完全対応 58
補足
補足 Promise resolves with RTCStatsReport.
完全対応 54
補足
補足 Promise-based version.
完全対応 あり
Chrome Android 完全対応 58
補足
完全対応 58
補足
補足 Promise resolves with RTCStatsReport.
完全対応 54
補足
補足 Promise-based version.
完全対応 あり
Edge Mobile ? Firefox Android ? Opera Android 完全対応 45Safari iOS ? Samsung Internet Android ?
getStreamByIdChrome 未対応 56 — 62Edge 完全対応 15Firefox 未対応 22 — 53IE ? Opera 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari ? WebView Android 未対応 56 — 62Chrome Android 未対応 56 — 62Edge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari iOS ? Samsung Internet Android 完全対応 6.0
icecandidate eventChrome 完全対応 24Edge 完全対応 15Firefox 完全対応 22IE ? Opera 完全対応 43Safari 完全対応 11WebView Android 完全対応 ありChrome Android 完全対応 25Edge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 完全対応 43Safari iOS ? Samsung Internet Android 完全対応 6.0
iceConnectionStateChrome 完全対応 26Edge 完全対応 15Firefox 完全対応 52IE ? Opera 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari 完全対応 11WebView Android 完全対応 ありChrome Android 完全対応 26Edge Mobile ? Firefox Android ? Opera Android 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari iOS ? Samsung Internet Android 完全対応 7.0
iceconnectionstatechange eventChrome 完全対応 28Edge 完全対応 15Firefox 完全対応 22IE ? Opera 完全対応 43Safari 完全対応 11WebView Android 完全対応 ありChrome Android 完全対応 28Edge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 完全対応 43Safari iOS ? Samsung Internet Android 完全対応 6.0
iceGatheringStateChrome 完全対応 25Edge 完全対応 15Firefox 完全対応 22IE ? Opera 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari 完全対応 11WebView Android 完全対応 ありChrome Android 完全対応 25Edge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari iOS ? Samsung Internet Android 完全対応 6.0
identityresult event
非推奨
Chrome 未対応 なしEdge 完全対応 ありFirefox 完全対応 22IE ? Opera 完全対応 43Safari ? WebView Android 未対応 なしChrome Android 未対応 なしEdge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 完全対応 43Safari iOS ? Samsung Internet Android 完全対応 6.0
idpassertionerror event
非推奨
Chrome 未対応 なしEdge 完全対応 ありFirefox 完全対応 22IE ? Opera 完全対応 43Safari ? WebView Android 未対応 なしChrome Android 未対応 なしEdge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 完全対応 43Safari iOS ? Samsung Internet Android 完全対応 6.0
idpvalidationerror event
非推奨
Chrome 未対応 なしEdge 完全対応 ありFirefox 完全対応 22IE ? Opera 完全対応 43Safari ? WebView Android 未対応 なしChrome Android 未対応 なしEdge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 完全対応 43Safari iOS ? Samsung Internet Android 完全対応 6.0
localDescriptionChrome 完全対応 24Edge 完全対応 15Firefox 完全対応 22IE ? Opera 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari 完全対応 11WebView Android 完全対応 ありChrome Android 完全対応 25Edge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari iOS ? Samsung Internet Android 完全対応 6.0
negotiationneeded eventChrome 完全対応 24Edge 完全対応 15Firefox 完全対応 22IE ? Opera 完全対応 43Safari 完全対応 11WebView Android 完全対応 ありChrome Android 完全対応 ありEdge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 完全対応 43Safari iOS ? Samsung Internet Android 完全対応 6.0
onaddstream
非推奨
Chrome 完全対応 24Edge 完全対応 15Firefox 完全対応 22IE ? Opera 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari 未対応 なしWebView Android 完全対応 ありChrome Android 完全対応 ありEdge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari iOS 未対応 なしSamsung Internet Android 完全対応 6.0
onconnectionstatechangeChrome 完全対応 72Edge 未対応 なしFirefox 未対応 なしIE 未対応 なしOpera 未対応 なしSafari 完全対応 11WebView Android 完全対応 72Chrome Android 完全対応 72Edge Mobile 未対応 なしFirefox Android 未対応 なしOpera Android 未対応 なしSafari iOS 未対応 なしSamsung Internet Android 未対応 なし
ondatachannelChrome 完全対応 25Edge 完全対応 ありFirefox 完全対応 22IE ? Opera 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari 完全対応 11WebView Android 完全対応 ありChrome Android 完全対応 25Edge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari iOS ? Samsung Internet Android 完全対応 6.0
onicecandidateChrome 完全対応 24Edge 完全対応 15Firefox 完全対応 22IE ? Opera 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari 完全対応 11WebView Android 完全対応 ありChrome Android 完全対応 ありEdge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari iOS ? Samsung Internet Android 完全対応 6.0
onicecandidateerrorChrome 未対応 なしEdge ? Firefox ? IE ? Opera ? Safari ? WebView Android 未対応 なしChrome Android 未対応 なしEdge Mobile ? Firefox Android ? Opera Android ? Safari iOS ? Samsung Internet Android ?
oniceconnectionstatechangeChrome 完全対応 28Edge 完全対応 15Firefox 完全対応 22IE ? Opera 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari 完全対応 11WebView Android 完全対応 ありChrome Android 完全対応 28Edge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari iOS ? Samsung Internet Android 完全対応 6.0
onicegatheringstatechangeChrome 完全対応 59Edge 完全対応 15Firefox 完全対応 22IE ? Opera 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari 完全対応 11WebView Android 完全対応 59Chrome Android 完全対応 59Edge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari iOS ? Samsung Internet Android 完全対応 7.0
onidentityresultChrome 未対応 なしEdge 完全対応 ありFirefox 完全対応 22IE ? Opera 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari ? WebView Android 未対応 なしChrome Android 未対応 なしEdge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari iOS ? Samsung Internet Android 完全対応 6.0
onidpassertionerrorChrome 未対応 なしEdge 完全対応 ありFirefox 完全対応 22IE ? Opera 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari ? WebView Android 未対応 なしChrome Android 未対応 なしEdge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari iOS ? Samsung Internet Android 完全対応 6.0
onidpvalidationerrorChrome 未対応 なしEdge 完全対応 ありFirefox 完全対応 22IE ? Opera 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari ? WebView Android 未対応 なしChrome Android 未対応 なしEdge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari iOS ? Samsung Internet Android 完全対応 6.0
onnegotiationneededChrome 完全対応 24Edge 完全対応 15Firefox 完全対応 22IE ? Opera 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari 完全対応 11WebView Android 完全対応 ありChrome Android 完全対応 ありEdge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari iOS ? Samsung Internet Android 完全対応 6.0
onpeeridentityChrome 未対応 なしEdge 完全対応 ありFirefox 完全対応 22IE ? Opera 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari ? WebView Android 未対応 なしChrome Android 未対応 なしEdge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari iOS ? Samsung Internet Android 完全対応 6.0
onremovestream
非推奨
Chrome 完全対応 24Edge 完全対応 15Firefox 未対応 22 — 60IE ? Opera 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari 未対応 なしWebView Android 完全対応 ありChrome Android 完全対応 ありEdge Mobile 完全対応 ありFirefox Android 未対応 44 — 60Opera Android 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari iOS 未対応 なしSamsung Internet Android 完全対応 6.0
onsignalingstatechangeChrome 完全対応 28Edge 完全対応 15Firefox 完全対応 22IE ? Opera 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari 完全対応 11WebView Android 完全対応 ありChrome Android 完全対応 28Edge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari iOS ? Samsung Internet Android 完全対応 6.0
ontrackChrome 完全対応 64Edge 完全対応 ありFirefox 完全対応 22IE ? Opera 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari 完全対応 11WebView Android 完全対応 64Chrome Android 完全対応 64Edge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari iOS ? Samsung Internet Android 完全対応 6.0
peerIdentityChrome 未対応 なしEdge 完全対応 ありFirefox 完全対応 22IE ? Opera 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari ? WebView Android 未対応 なしChrome Android 未対応 なしEdge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari iOS ? Samsung Internet Android 完全対応 6.0
peeridentity event
非推奨
Chrome 未対応 なしEdge 完全対応 ありFirefox 完全対応 22IE ? Opera 完全対応 43Safari ? WebView Android 未対応 なしChrome Android 未対応 なしEdge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 完全対応 43Safari iOS ? Samsung Internet Android 完全対応 6.0
pendingLocalDescriptionChrome 完全対応 70Edge 完全対応 ありFirefox 完全対応 22IE ? Opera 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari 完全対応 11WebView Android 完全対応 70Chrome Android 完全対応 70Edge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari iOS ? Samsung Internet Android 完全対応 6.0
pendingRemoteDescriptionChrome 完全対応 70Edge 完全対応 ありFirefox 完全対応 22IE ? Opera 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari 完全対応 11WebView Android 完全対応 70Chrome Android 完全対応 70Edge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari iOS ? Samsung Internet Android 完全対応 6.0
remoteDescriptionChrome 完全対応 24Edge 完全対応 15Firefox 完全対応 22IE ? Opera 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version and unprefixed.
未対応 38 — 43
補足
補足 Promise-based version.
Safari 完全対応 11WebView Android 完全対応 ありChrome Android 完全対応 ありEdge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version and unprefixed.
未対応 38 — 43
補足
補足 Promise-based version.
Safari iOS ? Samsung Internet Android 完全対応 6.0
removeStreamChrome 完全対応 24Edge 完全対応 15Firefox 未対応 22 — 51IE ? Opera 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari ? WebView Android 完全対応 ありChrome Android 完全対応 ありEdge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari iOS 未対応 11 — 12Samsung Internet Android 完全対応 6.0
removestream eventChrome 完全対応 24Edge 完全対応 15Firefox 未対応 22 — 60IE ? Opera 完全対応 43Safari 未対応 なしWebView Android 完全対応 ありChrome Android 完全対応 25Edge Mobile 完全対応 ありFirefox Android 未対応 44 — 60Opera Android 完全対応 43Safari iOS 未対応 なしSamsung Internet Android 完全対応 6.0
removeTrackChrome 完全対応 64Edge 完全対応 ありFirefox 完全対応 22IE ? Opera 完全対応 51Safari 完全対応 11WebView Android 完全対応 64Chrome Android 完全対応 64Edge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 完全対応 51Safari iOS ? Samsung Internet Android 完全対応 6.0
sctpChrome 完全対応 56Edge 完全対応 ありFirefox 完全対応 22IE ? Opera 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari ? WebView Android 完全対応 56Chrome Android 完全対応 56Edge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari iOS ? Samsung Internet Android 完全対応 6.0
setConfigurationChrome 完全対応 48Edge 完全対応 ありFirefox 完全対応 22IE ? Opera 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari 完全対応 11WebView Android 完全対応 48Chrome Android 完全対応 48Edge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari iOS ? Samsung Internet Android 完全対応 6.0
setIdentityProviderChrome 未対応 なしEdge 完全対応 ありFirefox 完全対応 22IE ? Opera 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari ? WebView Android 未対応 なしChrome Android 未対応 なしEdge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari iOS ? Samsung Internet Android 完全対応 6.0
setLocalDescriptionChrome 完全対応 51
補足
完全対応 51
補足
補足 Promise-based version.
完全対応 24
Edge 完全対応 15Firefox 完全対応 22IE ? Opera 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari 完全対応 11WebView Android 完全対応 51
補足
完全対応 51
補足
補足 Promise-based version.
完全対応 あり
Chrome Android 完全対応 51
補足
完全対応 51
補足
補足 Promise-based version.
完全対応 あり
Edge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari iOS ? Samsung Internet Android 完全対応 6.0
補足
完全対応 6.0
補足
補足 Promise-based version and unprefixed.
未対応 5.0 — 6.0
補足
補足 Promise-based version.
setRemoteDescriptionChrome 完全対応 51
補足
完全対応 51
補足
補足 Promise-based version.
完全対応 24
Edge 完全対応 15Firefox 完全対応 22IE ? Opera 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari 完全対応 11WebView Android 完全対応 51
補足
完全対応 51
補足
補足 Promise-based version.
完全対応 あり
Chrome Android 完全対応 51
補足
完全対応 51
補足
補足 Promise-based version.
完全対応 あり
Edge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari iOS ? Samsung Internet Android 完全対応 6.0
signalingStateChrome 完全対応 26Edge 完全対応 15Firefox 完全対応 22IE ? Opera 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari 完全対応 11WebView Android 完全対応 ありChrome Android 完全対応 26Edge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 完全対応 43
補足
完全対応 43
補足
補足 Promise-based version.
未対応 37 — 43
Safari iOS ? Samsung Internet Android 完全対応 6.0
signalingstatechange eventChrome 完全対応 28Edge 完全対応 15Firefox 完全対応 22IE ? Opera 完全対応 43Safari 完全対応 11WebView Android 完全対応 ありChrome Android 完全対応 28Edge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 完全対応 43Safari iOS 未対応 なしSamsung Internet Android 完全対応 6.0
track eventChrome 完全対応 64Edge 完全対応 ありFirefox 完全対応 22IE ? Opera 完全対応 43Safari 完全対応 11WebView Android 完全対応 64Chrome Android 完全対応 64Edge Mobile 完全対応 ありFirefox Android 完全対応 44Opera Android 完全対応 43Safari iOS ? Samsung Internet Android 完全対応 6.0

凡例

完全対応  
完全対応
未対応  
未対応
実装状況不明  
実装状況不明
非推奨。新しいウェブサイトでは使用しないでください。
非推奨。新しいウェブサイトでは使用しないでください。
実装ノートを参照してください。
実装ノートを参照してください。
使用するには、ベンダー接頭辞または異なる名前が必要です。
使用するには、ベンダー接頭辞または異なる名前が必要です。

関連情報

ドキュメントのタグと貢献者

このページの貢献者: mdnwebdocs-bot, mfuji09, takamin, dreissig.jahrhundert
最終更新者: mdnwebdocs-bot,