UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/64.0.3282.167 Chrome/64.0.3282.167 Safari/537.36
Steps to reproduce the problem:
1. check 'connectionState' in RTCPeerConnection
What is the expected behavior?
see http://w3c.github.io/webrtc-pc/#rtcpeerconnectionstate-enum et al
What went wrong?
Chrome mixes up connectionstate and emits a combined ice/dtls state as iceconnectionstatechange.
Migrating developers might actually be the bigger problem here. Adding connectionState as an alias for iceConnectionState might be a good first step.
Also this makes it look like chrome has a significantly higher iceconnection setup time (30%) than Firefox since in Chrome the setup time includes the DTLS handshake whereas in Firefox it does not.
Did this work before? N/A
Does this work in other browsers? Yes
Chrome version: 64.0.3282.167 Channel: n/a
OS Version:
Flash Version:
Comment 1 by krajshree@chromium.org
, Mar 19 2018