henbos

Do the implementations limit to 16 characters?

My understanding is that historically, the idea with adapter.js was to shim APIs that had consensus, allowing developers to write modern code without worrying about implementation status, but they could...

I applaud wanting to make web developers suffer less, and I admit I don't fully understand the state of things, I just think we need a plan so that people...

> RTCRtpScriptTransform appears to have [consensus](https://www.w3.org/2021/Process-20211102/#def-Consensus) from the WebRTC WG's September 2 I see, I was reacting quite strongly to this being a motivation for the PR: > Web developers...

@jan-ivar Are you open to the idea to only delaying inbound-rtp creation, not outbound-rtp creation? I'd hate for a 3 layer simulcast stream to show up as singlecast in getStats...

We did?? Spec currently says: > The lifetime of all RTP [monitored object](https://w3c.github.io/webrtc-stats/#dfn-monitored-object)s starts when the [RTP stream](https://w3c.github.io/webrtc-stats/#dfn-rtp-stream) is first used: When the first RTP packet is sent or received...

I'm **very** surprised the spec says "MAY generate statistics that are not documented", this is something I have fought valiantly against for years and seems to describe the legacy callback-based...

Other than the exceptions listed above, I consider webrtc-provisional-stats to mostly be a graveyard of unimplemented metrics. Most of which originate from webrtc-stats but moved due to lack of implementer...

For background, the last time this API was discussed in the WebRTC Working Group was at TPAC, where we decided to make the API a synchronous getter instead of a...

Chrome has already shipped video track stats, I am planning to do an Intent to Ship for the audio track stats as well. Shall I reuse this "standards-position" to cover...