- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Thu, 02 Mar 2023 12:22:48 +0000
- To: public-webrtc@w3.org
henbos has just created a new issue for https://github.com/w3c/webrtc-stats: == Clarify that metrics are undefined when their value is not yet determined or unknown == "4.2 Guidelines for implementing stats objects" already says to use undefined if "a feature is not applicable" and gives the example of an audio metric for a video stream. We may want to clarify that if a metric is not yet determined or not yet known then we should also report undefined. For example, a video stream will have an encoderImplementation, but which one will be used is not determined until after the encoder has been initialized. Chrome currently reports the string value "unknown" but this should be undefined. There is no encoderImplementation with the name "unknown" and we have not spec'ed this magic value so it shouldn't exist Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/736 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 12:22:49 UTC