- From: jonasesolsson via GitHub <sysbot+gh@w3.org>
- Date: Wed, 14 Nov 2018 13:18:31 +0000
- To: public-webrtc@w3.org
jonasesolsson has just created a new issue for https://github.com/w3c/webrtc-pc: == Partially connected peerconnection might have "new" connectionstate. == Assume we have a peerconnection with a since ice transport and a dtls transport running on top of it. During setup we might have these steps: ice transport | dtls transport | connectionState --- | --- | --- new | new | new checking | new | connecting connected | new | new <--- connected | connecting | connecting connected | connected | connected This seems really unintuitive, I'd expect the connectionState to stay as "connecting". In https://w3c.github.io/webrtc-pc/#dom-rtcpeerconnectionstate would it make sense to move the "some connected, some new" case from "new" to "connecting"? A similar thing might happen to the ice connection state if there's multiple ice transports and one connects while another remains "new", but that seems like more of an edge case. Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2031 using your GitHub account
Received on Wednesday, 14 November 2018 13:18:32 UTC