- From: jan-ivar via GitHub <sysbot+gh@w3.org>
- Date: Mon, 19 Dec 2016 22:06:29 +0000
- To: public-webrtc-logs@w3.org
@fippo Any way to limit the scope of what we need to gather is a plus IMHO. Yes, any record referenced by id would need to be included, but I don't see how this ends up being the complete set. An audio track should have no direct or indirect references to a video track (unless there are some back references I'm missing). FWIW Firefox effectively filters out (skips) other tracks when a track is given as selector. You still get ICE stats. You can try it [here](https://jsfiddle.net/jib1/ncw14v8f/) (unless the diff is a fluke, it looks like we even filter out ICE candidates by track, who knew?) That said, we haven't implemented all stats yet, so what to include in the presence of a selector in general is a good question (when should we include data channel stats for instance? Can data channels be selectors?) -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/116#issuecomment-268092437 using your GitHub account
Received on Monday, 19 December 2016 22:06:35 UTC