- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Wed, 31 May 2023 13:00:32 +0000
- To: public-webrtc-logs@w3.org
I would like webrtc-stats to contain all metrics that have at least one browser implementation. I think it makes perfect sense that we added "at risk" notes after some of the recently added audio metrics became controversial. Right now there are a small number of metrics that have been implemented in Chromium like [contentType](https://w3c.github.io/webrtc-provisional-stats/#dom-rtcoutboundrtpstreamstats-contenttype) based on the [video-content-type](https://webrtc.googlesource.com/src/+/refs/heads/main/docs/native-code/rtp-hdrext/video-content-type) header extension that I would rather move to webrtc-stats with a note. As for most other metrics (except for a couple of other examples), the https://w3c.github.io/webrtc-provisional-stats/ doc is currently a graveyard of never-implemented and no-interest-to-ever-implement metrics, so I'd rather see us sunset that document in favor of one stats spec to rule them all. -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/749#issuecomment-1570190816 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 31 May 2023 13:00:34 UTC