Implement RTCTransportStats
Categories
(Core :: WebRTC, task, P3)
Tracking
()
backlog | webrtc/webaudio+ |
People
(Reporter: pehrsons, Unassigned)
References
(Depends on 1 open bug, Blocks 4 open bugs)
Details
We have the WebIDL for RTCCodecStats but it's not being populated. Spec at [1]. [1] https://w3c.github.io/webrtc-stats/archives/20151023/webrtc-stats.html#transportstats-dict*
Updated•9 years ago
|
Comment 1•7 years ago
|
||
Mass change P2->P3 to align with new Mozilla triage process.
Comment 2•5 years ago
|
||
Note: remember to deprecate our RTCIceCandidatePairStats.selected property once we implement this. Our |selected| attribute is something we added a long time ago, mostly for about:webrtc.
In the spec, which pair is selected for a particular transport appears to be indicated by RTCTransportStats.selectedCandidatePairId, since different transports will have different candidate pools.
Once this if fixed, web sites that want to learn which pair is used, can remove their workarounds for Firefox, and we should also update about:webrtc to use the spec way.
Comment 3•4 years ago
|
||
The crypto-suite.https.html wpt has a bunch of expected failures due to this.
Updated•3 years ago
|
Updated•2 years ago
|
Comment 4•1 year ago
|
||
I think it makes sense to do RTCIceTransport first, since some of the stats will either be based directly on that, or at the very least the same API in MediaTransportHandler that it uses.
Comment 5•2 months ago
|
||
We might be able to do a partial implementation here, and expand both this and RTCIceTransport afterward.
Description
•