Open Bug 1225723 Opened 9 years ago Updated 2 years ago

Implement RTCTransportStats

Categories

(Core :: WebRTC, task, P3)

Product:
Core
Component:
WebRTC
Type:
task

Tracking

()

Blocking Flags:
backlog webrtc/webaudio+

People

(Reporter: pehrsons, Unassigned)

References

(Depends on 1 open bug, Blocks 3 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*
Blocks: webrtc_spec
backlog: --- → webrtc/webaudio+
Rank: 25
Priority: -- → P2
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
Blocks: 1533020

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.

The crypto-suite.https.html wpt has a bunch of expected failures due to this.

Type: defect → task
Severity: normal → S3

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.

Depends on: 1307994
You need to log in before you can comment on or make changes to this bug.