- From: Philipp Hancke via GitHub <sysbot+gh@w3.org>
- Date: Fri, 28 Feb 2025 22:46:54 +0000
- To: public-webrtc-logs@w3.org
I'll add a WPT that ensures addTrack+SLD does *not* create stats and try to find a better name for the two existing tests.
I also found this gem:
```
const pc1 = new RTCPeerConnection();
pc1.createDataChannel('zort')
stats = await pc1.getStats();
```
Firefox has a dataChannelIdentifier 65535 (aka -1) which looks like a bug.
Both Chromium and Firefox expose the datachannel stats before connection (good) and before negotiation (bad)
That suggests we should do the same for RTP.
I'll stick to what I said here three years ago: "fix the spec and then fix some implementations a bit and then write moar tests"
--
GitHub Notification of comment by fippo
Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/797#issuecomment-2691673195 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 28 February 2025 22:46:55 UTC