- From: Philipp Hancke via GitHub <sysbot+gh@w3.org>
- Date: Fri, 17 Jun 2022 10:15:34 +0000
- To: public-webrtc@w3.org
fippo has just created a new issue for https://github.com/w3c/webrtc-stats: == guidelines for getStats() results caching/throttling are a bit vague == https://w3c.github.io/webrtc-stats/#guidelines-for-getstats-results-caching-throttling says | When the state of the RTCPeerConnection visibly changes [clear the cache] This doesn't define what "visibly changes" means. The onicecandidate or addIceCandidate methods will make new objects (of type local-candidate and remote-candidate) show up (which is assertable in a test). The icegatheringstatechange event does not change the objects (I think) so should *not* invalidate. Maybe we should add a "maybe flush the cache" to descriptions like https://w3c.github.io/webrtc-pc/#dom-peerconnection-addicecandidate ? Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/642 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 17 June 2022 10:15:36 UTC