Open Bug 1371391 Opened 8 years ago Updated 2 months ago

Implement remaining fields in RTCIceCandidatePairStats

Categories

(Core :: WebRTC: Networking, enhancement, P3)

enhancement

Tracking

()

People

(Reporter: mjf, Assigned: mjf)

References

(Blocks 2 open bugs)

Details

(Keywords: dev-doc-needed, webcompat:platform-bug)

User Story

https://mozilla-hub.atlassian.net/browse/FFXP-677
platform-scheduled:2025-06-01

Attachments

(5 files)

Our implementation of RTCIceCandidatePairStats is still missing some of the fields from the spec: https://w3c.github.io/webrtc-stats/#candidatepair-dict* remaining: writeable readable totalRoundTripTime currentRoundTripTime availableOutgoingBitrate availableIncomingBitrate requestsReceived requestsSent responsesReceived responsesSent retransmissionsReceived retransmissionsSent consentRequestsSent
Blocks: 1359872
Rank: 29
Priority: -- → P2
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
Severity: normal → S3

We implement spec gaps based on external partner needs. This has not been flagged by anyone and as such is low priority / backlog.

currentRoundTripTime would be the priority.

User Story: (updated)
User Story: (updated)
No longer blocks: webrtc-triage

The mandatory to implement ones are https://w3c.github.io/webrtc-pc/#mandatory-to-implement-stats:

  • transportId, localCandidateId, remoteCandidateId, state, nominated, bytesSent, bytesReceived, totalRoundTripTime, responsesReceived, currentRoundTripTime
Assignee: nobody → mfroman
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: