Open Bug 1225720 Opened 8 years ago Updated 1 year ago

Implement RTC "sender", "receiver" and "track" (track attachment) stats (and make them simulcast aware)

Categories

(Core :: WebRTC, task, P3)

task

Tracking

()

People

(Reporter: pehrsons, Unassigned)

References

(Blocks 3 open bugs)

Details

(Whiteboard: [wpt-triaged])

backlog: --- → webrtc/webaudio+
Rank: 25
Priority: -- → P2
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3

These stats have changed names as of https://github.com/w3c/webrtc-stats/issues/298

Summary: Implement RTCMediaStreamStats and RTCMediaStreamTrackStats → Implement RTC track attachment stats

I don't see us implementing "track" stats without the newer analogous "sender" and "receiver" stats, so renaming the issue to include that.

Summary: Implement RTC track attachment stats → Implement RTC "sender", "receiver" and "track" (track attachment) stats
Blocks: 1533020

When we do this, we should make sure to report correct numbers for simulcast.

Summary: Implement RTC "sender", "receiver" and "track" (track attachment) stats → Implement RTC "sender", "receiver" and "track" (track attachment) stats (and make them simulcast aware)
Type: defect → task
Whiteboard: [wpt-triaged]

Jan-Ivar the names in the spec appear to have changed a bit, do you think it would be reasonable to rename this "Implement stats in the RTCMediaHandlerStats hierarchy"?

Flags: needinfo?(jib)

It wouldn't be incorrect, except I find it simpler to navigate stats by type field names (which are exposed to JS) than by dictionary names (which aren't). My favorite section added to the spec so far is the appendix: Summary of WebRTC stats fields per type.

But both should be stable by now, so I guess it doesn't matter.

Flags: needinfo?(jib)
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.