Closed
Bug 964334
Opened 11 years ago
Closed 6 years ago
[meta] Developer debugging tools for WebRTC
Categories
(Core :: WebRTC, defect)
Core
WebRTC
Tracking
()
RESOLVED
FIXED
People
(Reporter: jesup, Unassigned)
Details
(Keywords: meta)
about:webrtc is a good start. Meta bug for other tools (or improvements to about:webrtc) that will help developers debug their webrtc applications.
We should loop in some of the devtools people too (adding dcamp; he may know better who would be interested)
Comment 1•11 years ago
|
||
What would about:webrtc do? What would be the scope of the tool? Providing browser-level info about webrtc (devices found and global network logs)? Or would it be for a specific session? Who's the audience?
The scope of a devtools panel is "one window". If you want to expose info and provide tools for one window and web developers (not gecko developers), maybe it's best to use a devtools panel.
Comment 2•11 years ago
|
||
So, right now about:webrtc provides browser-level statistics and logging. This includes information on connection establishment (ICE state) and RTP statistics (packets/bytes sent/received, and jitter). It would not be terribly difficult to provide information scoped to a single window (indeed, a lot of this stats info is being standardized by the w3c), but the logging is a little challenging, since that is not currently separated out by window. about:webrtc was intended first as something to be used by gecko devs, but should still be useful for web developers.
Comment 3•6 years ago
|
||
The meta keyword is there, the bug doesn't depend on other bugs and there is no activity for 12 months.
:drno, maybe it's time to close this bug?
Flags: needinfo?(drno)
Comment 4•6 years ago
|
||
I can't think of any work we have in mind for this right now.
Status: NEW → RESOLVED
Closed: 6 years ago
Flags: needinfo?(drno)
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•