This reverts commit 3eceaf46695518f25bef43f155f82ed174827197. Reason for revert: Original change's description: > Migrate WebRTC documentation to new renderer > > Bug: b/258408932 > Change-Id: Ib96f39fe0c3912f9746bcc09d079097a145d6115 > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/290987 > Reviewed-by: Harald Alvestrand <hta@webrtc.org> > Commit-Queue: Artem Titov <titovartem@webrtc.org> > Cr-Commit-Position: refs/heads/main@{#39205} Bug: b/258408932 Change-Id: I16cb4088bee3fc15c2bb88bd692c592b3a7db9fe No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/291560 Bot-Commit: rubber-stamper@appspot.gserviceaccount.com <rubber-stamper@appspot.gserviceaccount.com> Owners-Override: Artem Titov <titovartem@webrtc.org> Commit-Queue: Artem Titov <titovartem@webrtc.org> Cr-Commit-Position: refs/heads/main@{#39209}
720 B
720 B
getStats in WebRTC
The WebRTC getStats API is specified in https://w3c.github.io/webrtc-stats/ and allows querying information about the current state of a RTCPeerConnection API and some of its member objects.
Adding new statistics to Chrome
When adding a new standardized RTCStatsMember it is necessary to add
it to the Chrome allowlist
chrome/test/data/webrtc/peerconnection_getstats.js
before landing the WebRTC change. This mechanism prevents the accidential
addition and exposure of non-standard attributes and is not required for
RTCNonStandardStatsMember which is not exposed to the web API.