Chrome throws an exception for
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.)
Chrome throws an exception for
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.)