- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Thu, 27 Feb 2025 15:53:54 +0000
- To: public-webrtc-logs@w3.org
Yes I didn't mean to suggest the divide by zero hazard was limited to this API. The difference is something like `framesDecoded` is tied to real-world reception of RTP which won't vary by user agent. I think the concern in this case is: 1. lack of cap on frequency might lead two browsers to implement vastly different intervals, e.g. 1 vs 15 seconds. 2. whether an anticipated use case is A/B codec testing where a website might tune its interval to the fastest browser -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/webrtc-stats/pull/794#issuecomment-2688380807 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 27 February 2025 15:53:55 UTC