| Summary: | "outbound-rtp" and "inbound-rtp" WebRTC stats appear prematurely | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | jib |
| Component: | WebRTC | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW --- | ||
| Severity: | Normal | CC: | webkit-bug-importer, youennf |
| Priority: | P2 | Keywords: | InRadar |
| Version: | Safari 15 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
For inbound-rtp see https://jsfiddle.net/jib1/b32myw94/9/ (here Firefox fails as well, which is https://bugzil.la/1751532) For WPT see https://github.com/w3c/webrtc-stats/issues/619. |
Other browsers tested: Chrome: FAIL (https://crbug.com/1291019) Firefox: OK Edge: FAIL What steps will reproduce the problem? (1) Open https://jsfiddle.net/jib1/h4swg3xb/8/ What is the expected result? 0 outbound-rtp What happens instead? 1 outbound-rtp The spec [1] says: "The lifetime of all RTP monitored objects starts when the RTP stream is first used: When the first RTP packet is sent or received on the SSRC it represents, or when the first RTCP packet is sent or received that refers to the SSRC of the RTP stream." The fiddle doesn't even establish a peer connection. [1] https://w3c.github.io/webrtc-stats/#the-rtp-statistics-hierarchy