- From: Soares Chen via GitHub <sysbot+gh@w3.org>
- Date: Thu, 06 Jul 2017 03:50:24 +0000
- To: public-webrtc-logs@w3.org
soareschen has just created a new issue for https://github.com/w3c/webrtc-pc:
== setConfiguration can "unset" some configurations ==
This issue is similar to #1447. The last step of setConfiguration saves the provided configuration object to the `[[Configuration]]` internal slot, overriding the previous values. #1447 covers the fields with default values, so they cannot be unset. But fields like `iceServers`, `peerIdentity` and `certificates` can seemingly be "unset" from the user-visible configuration. For example:
```javascript
const pc = new RTCPeerConnection({
iceServers: [...],
certificates: [...],
peerIdentity: ...
});
pc.setConfiguration({});
const config = pc.getConfiguration();
config.iceServers // undefined
config.certificates // undefined
config.peerIdentity //undefined
```
Note that this only affects the user-visible configuration. Since the spec lets `RTCPeerConnection` save the actual configuration internally elsewhere, the "unset" never affects the actual connection.
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1454 using your GitHub account
Received on Thursday, 6 July 2017 03:50:31 UTC