Skip to content

RTCPeerConnection constructor parameters are probably wrong #16595

@foolip

Description

@foolip

Some of the parameters for the RTCPeerConnection constructor have very different data for Chrome desktop and Android:

"description": "<code>configuration.iceCandidatePoolSize</code> parameter",
"support": {
"chrome": {
"version_added": "23"
},
"chrome_android": {
"version_added": "57"
},

"description": "<code>configuration.iceServers</code> parameter",
"spec_url": "https://w3c.github.io/webrtc-pc/#dom-rtcconfiguration-iceservers",
"support": {
"chrome": {
"version_added": "23"
},
"chrome_android": {
"version_added": "57"
},

"description": "<code>configuration.iceTransportPolicy</code> parameter",
"spec_url": "https://w3c.github.io/webrtc-pc/#dom-rtcconfiguration-icetransportpolicy",
"support": {
"chrome": {
"version_added": "23"
},
"chrome_android": {
"version_added": "57"
},

"description": "<code>configuration.peerIdentity</code> parameter",
"support": {
"chrome": {
"version_added": "23"
},
"chrome_android": {
"version_added": "57"
},

This is probably wrong and should be double checked.

cc @queengooborg

Metadata

Metadata

Assignees

Labels

data:apiCompat data for Web APIs. https://developer.mozilla.org/docs/Web/API

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions