- From: Anne van Kesteren via GitHub <sysbot+gh@w3.org>
- Date: Tue, 22 Jun 2021 12:03:32 +0000
- To: public-webrtc-logs@w3.org
annevk has just created a new issue for https://github.com/w3c/webrtc-pc:
== Unclear how URLs are processed ==
Chrome throws an exception for
```js
new RTCPeerConnection({ iceServers: [{ urls:["stun:turn.example.org/test"] }] });
```
whereas Firefox and Safari do not.
Where does https://w3c.github.io/webrtc-pc/#dom-peerconnection process these?
Some processing appears to happen in https://w3c.github.io/webrtc-pc/#set-the-configuration but that does not seem to be invoked from the constructor. (That also suggests using a URL parser that browsers do not have, which seems somewhat dubious.)
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2660 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 22 June 2021 12:04:15 UTC