Add loss, jitter, and RTT to about:webrtc

RESOLVED FIXED in mozilla30

Status

()

Core
WebRTC: Audio/Video
RESOLVED FIXED
5 years ago
4 years ago

People

(Reporter: abr, Assigned: jib)

Tracking

(Blocks: 1 bug)

unspecified
mozilla30
Points:
---
Dependency tree / graph
Bug Flags:
in-testsuite +

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

Comment hidden (empty)
(Reporter)

Updated

5 years ago
Blocks: 964161

Comment 1

5 years ago
Once these are added to the stats API, we need to display them on about:webrtc.

Updated

5 years ago
Depends on: 970686
Loss and jitter are covered by Bug 970686, so this is the last patch (i.e. no need to leave this open)
Assignee: nobody → jib

Comment 4

4 years ago
Comment on attachment 8391431 [details] [diff] [review]
Add RTT to about:webrtc

Review of attachment 8391431 [details] [diff] [review]:
-----------------------------------------------------------------

Looks pretty much good, with just a minor concern.

::: toolkit/content/aboutWebrtc.xhtml
@@ +157,5 @@
>      if (stat.bytesReceived !== undefined) {
>        statsString += " (" + round00(stat.bytesReceived/1024) + " Kb)";
>      }
> +    statsString += " Lost: " + stat.packetsLost + " Jitter: " + stat.jitter;
> +    if (stat.mozRtt !== undefined) {

Is this expected to be undefined in normal operation?
Attachment #8391431 - Flags: review?(docfaraday) → review+
(In reply to Byron Campen [:bwc] from comment #4)
> > +    if (stat.mozRtt !== undefined) {
> 
> Is this expected to be undefined in normal operation?

Yes, glad you asked. RTT is only included in the RTCP case on the outbound side.
Keywords: checkin-needed
https://hg.mozilla.org/mozilla-central/rev/449272159e81
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla30
You need to log in before you can comment on or make changes to this bug.