- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Thu, 02 Mar 2023 22:12:44 +0000
- To: public-webrtc-logs@w3.org
_(I'm interpreting defined/undefined in this thread has missing/present/[exists](https://infra.spec.whatwg.org/exists). See https://github.com/w3c/webrtc-stats/issues/737. LMK if that's not right)_ While there might be some value today in knowing immediately whether a browser supports a stat or not, such value should diminish over time, so omitting members until they can be accurately reported seems superior to me to the alternatives. There's probably some precedence here with stats objects of type [remote-inbound-rtp](https://w3c.github.io/webrtc-stats/#dom-rtcstatstype-remote-inbound-rtp) and [remote-outbound-rtp](https://w3c.github.io/webrtc-stats/#dom-rtcstatstype-remote-outbound-rtp) which don't appear until rtcp packets have been received (comment out the `await wait(5000)` in [this fiddle](https://jsfiddle.net/jib1/moz71L7h/). -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/736#issuecomment-1452620688 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 2 March 2023 22:12:46 UTC