- From: jan-ivar via GitHub <sysbot+gh@w3.org>
- Date: Tue, 20 Dec 2016 18:55:33 +0000
- To: public-webrtc-logs@w3.org
FF has implemented the selector since [2013](https://bugzilla.mozilla.org/show_bug.cgi?id=902003); it's been in the spec even longer. I think it's here to stay. The spec [says](http://w3c.github.io/webrtc-pc/#stats-selector): *"For a track to be a valid selector, it MUST be a MediaStreamTrack that is sent or received by the RTCPeerConnection object on which the stats request was issued. ... the browser emits (in the JavaScript) a set of statistics that it believes is relevant to the selector."* Firefox does [exactly that](https://github.com/w3c/webrtc-stats/issues/116#issuecomment-268092437). Sure, flesh out the line of relevance, but no 180's please over details. Benefit example: Users can get a specific track stats without looping over records: ```js let rtp = [...(await pc.getStats(track)).values()].find(stat => stat.type == "outboundrtp"); let videoPackets = rtp.packetsSent; ``` -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/116#issuecomment-268326206 using your GitHub account
Received on Tuesday, 20 December 2016 18:55:40 UTC