W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > September 2019

[webrtc-stats] RTCPeerConnectionStats is missing state stats (connection, ice, gathering, signaling) (#484)

From: henbos via GitHub <sysbot+gh@w3.org>
Date: Tue, 10 Sep 2019 13:42:30 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issues.opened-491680938-1568122949-sysbot+gh@w3.org>
henbos has just created a new issue for https://github.com/w3c/webrtc-stats:

== RTCPeerConnectionStats is missing state stats (connection, ice, gathering, signaling) ==
[RTCPeerConnectionStats](https://w3c.github.io/webrtc-stats/#pcstats-dict*) does not contain PC state information.

- If we fix #483 we have iceState on a per-transport basis. Would it make sense to compute [iceConnectionState](https://w3c.github.io/webrtc-pc/#dom-peerconnection-ice-connection-state) and expose it on the PC level?
- Should we also expose [connectionState](https://w3c.github.io/webrtc-pc/#dom-peerconnection-connection-state)?
- Should we expose [iceGatheringState](https://w3c.github.io/webrtc-pc/#dom-peerconnection-ice-gathering-state)?
- Should we expose [signalingState](https://w3c.github.io/webrtc-pc/#dom-peerconnection-signaling-state)?

Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/484 using your GitHub account
Received on Tuesday, 10 September 2019 13:42:32 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:22:28 UTC