← back to v141 · webrtc-getstats-align-implementations-on-when-rtp-stats-should-be-created
conformance · v141
v141 · webrtc-getstats-align-implementations-on-when-rtp-stats-should-be-created — conformance probe
6 assertions drawn from the spec. Each is a single contract the spec text makes. Pass/fail reflects what this browser executed; blocked means the contract was not run because it needs user mediation, hardware, or another unavailable precondition. Open the page in Chrome stable / canary / Firefox / Safari to compare.
0
pass
0
fail
0
blocked
6
total
| id | contract | kind | verdict | detail |
|---|---|---|---|---|
rtcpeerconnection-exists |
RTCPeerConnection is exposed; getStats() lives on the connection and per-RTP-receiver/sender objects. | exists | … | |
rtcpeerconnection-getstats |
RTCPeerConnection.prototype.getStats is a Promise-returning function; the alignment change affects what entries it produces. | script | … | |
rtcrtpsender-getstats |
RTCRtpSender.prototype.getStats exists; per-sender stats collection is one place where the create-timing alignment matters. | script | … | |
rtcrtpreceiver-getstats |
RTCRtpReceiver.prototype.getStats exists; the spec aligns when inbound-rtp entries appear in the report from receivers. | script | … | |
rtcstatsreport-is-map-like |
RTCStatsReport is exposed and is map-like (forEach / get); this is the dictionary getStats() resolves to. | script | … | |
createoffer-exists |
RTCPeerConnection.prototype.createOffer exists; SDP negotiation is the point at which SSRC information becomes known and stats objects may or may not be created. | script | … |