Closed
Bug 1377225
Opened 8 years ago
Closed 7 years ago
Calling getStats on closed RTCPeerConnection resolves to undefined
Categories
(Core :: WebRTC: Signaling, defect, P3)
Tracking
()
RESOLVED
DUPLICATE
of bug 1056433
People
(Reporter: mroberts, Unassigned)
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36
Steps to reproduce:
The legacy callback-based getStats as well as the Promise-based getStats method return undefined instead of an RTCStatsReport when called on a closed RTCPeerConnection, as specified by http://w3c.github.io/webrtc-pc/#rtcpeerconnection-interface-extensions-2
To test this out, run the following code:
(async () => {
const pc = new RTCPeerConnection()
pc.close()
const report1 = await new Promise((resolve, reject) => pc.getStats(null, resolve, reject))
const report2 = await pc.getStats(null)
console.log(report1)
console.log(report2)
})()
Actual results:
I saw the following printed in the console:
undefined
undefined
Expected results:
I should see the following printed in the console:
RTCStatsReport { size: 0 }
RTCStatsReport { size: 0 }
Updated•8 years ago
|
Component: Untriaged → WebRTC
Product: Firefox → Core
Updated•8 years ago
|
Rank: 20
Component: WebRTC → WebRTC: Signaling
Priority: -- → P2
Comment 1•7 years ago
|
||
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•