Re: [webrtc-stats] Don't expose so many RTCCodecStats! (#662)

somewhat related: (part of) the codec stats bloat was discussed in #614 and deemed as a Chrome implementation bug IIUC:
> From [testing](https://jsfiddle.net/jib1/5v4qdr79/) I see Chrome creating a full set of "codec" entries (46) for each transceiver (10 transceivers = 460 "codec" entries), even though there's only 1 "transport" (because BUNDLE). I read the spec as sayng that 10 transceivers should produce 46 "codec" instances (in Chrome), not 460.



-- 
GitHub Notification of comment by dontcallmedom
Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/662#issuecomment-1232644602 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 31 August 2022 08:41:59 UTC