WebRTC M104 Release Notes
Harald Alvestrand
WebRTC M104 Release Notes
Branch: WebRTC M104 branch - cut date June 9, 2022
These notes cover some features from the M102 and M103 branches as well.
Summary
WebRTC M104, currently available in Chrome's beta channel, contains 4 new features and over 32 bug fixes, enhancements and stability/performance improvements. We encourage all developers to run versions of Chrome on the Canary, Dev, and Beta channels frequently and quickly report any issues found. Please take a look at this page, for some pointers on how to file a good bug report. The help we have received has been invaluable!
Note that the WebRTC release notes only cover WebRTC specific changes. Build, test and trivial code changes are not included. Follow the Chromium and Chrome releases blog for further updates on important changes in Chrome releases.
We strongly recommend WebRTC developers to fully test their services in Chrome beta to ensure stability for end-users.
The Chrome release schedule can be found here
PSAs
Plan B is now gone from Chrome
ChromeOS had an extension to the deprecation of Plan B. This is now removed; all regular Chrome releases now have Unified Plan only.
Region Capture is now available
When capturing a tab, it is now possible to select just part of the tab for capture.
See the Chrome blog for details
Usrsctp is now deleted from Chrome
After switching to using the dcSCTP library in earlier versions, the usrsctp dependency is now removed from both Chrome and WebRTC.
RTCPeerConnection’s mediaConstraints argument is deprecated
This argument, which was a non-standard feature, has largely been a no-op for a long time, except for a few special cases. Those cases are now removed, and the argument will be removed shortly.
Highlights
H264 422 decoding is supported as of M102
The (faster) AV1 decoder dav1d is now available - use the command line flag --force-fieldtrials="WebRTC-Dav1dDecoder" to enable it. This will soon become the default AV1 decoder.