- From: Jan-Ivar Bruaroey via GitHub <noreply@w3.org>
- Date: Wed, 06 Aug 2025 21:07:03 +0000
- To: public-webrtc-logs@w3.org
> Firefox showing `dataChannelIdentifier: 65535` pre-negotiation... wait, did we not discuss that recently? This bug was fixed last week in [bug 1974443](https://bugzilla.mozilla.org/show_bug.cgi?id=1974443) (Firefox 143). > Showing dataChannelIdentifier 0 after negotiation seems risky, I'm not able to reproduce that. But I am seeing some differences with https://jsfiddle.net/jib1/2qk9as1n/ Safari, Chrome, Firefox: <img height="600" alt="Image" src="https://github.com/user-attachments/assets/2b677275-1bfd-418a-a63f-fb842a3194db" /> Observations: 1. Only Firefox exposes `"data-channel"` stats ahead of sLD (`after: [null]` vs `after: []`) 2. All browsers expose `"data-channel"` stats after sLD but with a `null` dataChannelIdentifier, which might needlessly trip up readers for scant benefit 3. All browsers initialize dataChannelIdentifier on returning to stable 4. The [spec](https://w3c.github.io/webrtc-stats/#dcstats-dict*) seems written to do basic counting at the API level, not the underlying transport level, aligning with Firefox: <img width="835" height="522" alt="Image" src="https://github.com/user-attachments/assets/8f66b27d-deee-4be2-b843-34023f38a78d" /> but this may have been a mistake that didn't anticipate data channels in workers. Having `pc.getStats()` thread-hop to every worker to collect counts seems inefficient, especially since this needs to be done whether callers care about these stats or not. Are other browsers counting at the underlying transport level? I so, I think we're open to redefining this. There appear to be no WPT tests for this. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/805#issuecomment-3161616138 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 6 August 2025 21:07:04 UTC