- From: Dominique Hazael-Massieux via GitHub <sysbot+gh@w3.org>
- Date: Tue, 30 Aug 2022 11:46:22 +0000
- To: public-webrtc-logs@w3.org
Following the good work done in #622, I have updated my [implementation report](https://w3c.github.io/webrtc-interop-reports/webrtc-stats-report.html) to match the latest data from WPT, taking into account some of the additional input gathered in #622. I still have the following stats for which I'm not clear whether they're implemented in Chromium: `remote-inbound-rtp.framesDropped`, `remote-outbound-rtp.roundTripTime`. @henbos / @fippo? There are a bunch that seems to be[ only implemented in Chromium](https://w3c.github.io/webrtc-interop-reports/webrtc-stats-report.html#singleimpl) based on the [WPT supported stats test](https://wpt.fyi/results/webrtc-stats/supported-stats.json?label=experimental&label=master&aligned) (although some of these may be false positives due to timing / environment issues, similar to some of the situations documented for Chromium in my [manual annotations](https://github.com/w3c/webrtc-interop-reports/blob/main/annotations-stats.json)). @jan-ivar @youennf any chance you could help review the list of "single implementation" stats and share a sense of whether they are in fact implemented, under development, or not on the roadmap? -- GitHub Notification of comment by dontcallmedom Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/595#issuecomment-1231554184 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 30 August 2022 11:46:24 UTC