Create an origin trial that when enabled allows users to change the size of the WebRTC jitter buffer and read a new statistic counting the number of times the buffer is flushed. This will be allow us to explore the performance impact of tweaking this value. If it proves useful we'll either tweak the WebRTC implementation or start working to add it the standardized WebRTC APIs.


Status in Chromium


Proposed (tracking bug)

Consensus & Standardization

After a feature ships in Chrome, the values listed here are not guaranteed to be up to date.

  • No signal
  • No signal
  • No signals


Last updated on 2022-01-04