M121 Release Notes

[Harald Alvestrand]

WebRTC M121 is going to be released as part of Chrome M121, currently planned for release on January 23, 2024.

We had three PSAs for M121:

• PSA: DTLS client hello extension permutation will be enabled soon, do interop testing now (testing should start in January, many thanks for the feedback)

• PSA: PeerConnectionFactoryDependencies changes how media support is enabled

• PSA: scoped_refptr is moving from rtc:: to webrtc::

and one deprecation:

• PSA: WebRtcAllowLegacyTLSProtocols enterprise policy to be removed from Chrome M121

Chrome 121 also adds support for “element capture” described in this blog post:

https://developer.chrome.com/docs/web-platform/element-capture?hl=en

In addition to that there is an experiment/rollout ongoing for an improved getUserMedia dialog that allows users to give permission once. See this blog post:

https://developer.chrome.com/blog/one-time-permissions?hl=en

The following issues were marked as fixed or verified and had at least one commit in M121 (build, test and trivial code changes are not included):

Issue	Summary	Component
webrtc:11341	Implement injectable video encoder selector.	Video
chromium:1498378	Measure CPU frequency oversubscription	Blink>WebRTC>Perf
webrtc:15661	ByteBufferReader should use uint8_t not char	Internals
webrtc:10261	Drop DTLS 1.0, TLS 1.0, TLS 1.1 Support From WebRTC in M88	Network>DTLS
webrtc:12598	AsyncResolver (DNS resolution) needs a redesign
webrtc:15699	Improve performance of dcsctp::OutstandingData::Push	DataChannel
webrtc:14600	dcSCTP enters deferred stream reset processing mode and never exits	DataChannel
webrtc:15697	RTCAudioSession isActive doesn't reflect the actual state of AVAudioSession	Audio
webrtc:15574	Consider how "No media" is signalled when creating a PeerConnection	Cleanup
chromium:1381982	Deadlock in WebRTC metronome	Blink>WebRTC
chromium:1354491	Make the TaskQueuePacedSender bursty.	Blink>WebRTC >PeerConnection
chromium:1508337	Cloning RTCEncodedAudioFrames drops CSRCs	Blink>WebRTC >PeerConnection
chromium:1501500	neteq_rtp_fuzzer: Integer-overflow in webrtc::DecisionLogic::ExpectedPacketAvailable	Blink>WebRTC >Audio
webrtc:15579	Add mimeType to insertable streams metadata	PeerConnection
webrtc:15407	Avoid concurrent access to notifier and prevent it being called more than once	Video
webrtc:15656	Unify plumbering of widely used components.	Internals
webrtc:15636	IllegalArgumentException during HW VP8 envoder configuration	Video
webrtc:15181	VideoCaptureDS::StopCapture can deadlock with IncomingFrame
chromium:1247761	Region Capture - API for Cropping Self-Capture Video Tracks - Tracking Bug	Blink >GetDisplayMedia
webrtc:15579	Add mimeType to insertable streams metadata	PeerConnection
chromium:1496224	Encoded Transforms always copies audio packet payload even if JS doesn't interact with it	Blink>WebRTC >PeerConnection
chromium:1505128	Make UserMediaClient::pending_display_requests_ non-nullable	Blink>GetUserMedia,Blink >GetDisplayMedia
chromium:1498365	Enabling MF VEA H264 CBP encoding causes H264 HP instead of VP9 to be used by MF VEA	Blink>WebRTC>Video
chromium:1132854	Remove WebRtcAllowLegacyTLSProtocols enterprise policy	Blink>WebRTC >PeerConnection

For the full list of commits please refer to the git log between this branch and the previous branch. See here for a description of what the release notes contain.

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.

These release notes were prepared by Philipp Hancke.

[[MSFT] Diego Perez Botero]

The following WebRTC H264 fix is in the process of being brought to M121 as well:  1513312 - UseMultiPlaneFormatForSoftwareVideo DISABLED on Chromium M120+ is causing pink H264 video tinting in WebRTC media streams for Windows devices with old GPUs - chromium

[Mike Grabski]

The link points to refs/branch-heads/6099 which is the M120 release, while I believe M121 should be refs/branch-heads/6167 

[Philipp Hancke]

oops, thanks for catching that. That part gets copy-pasted, I'll pay more attention next time

--
This list falls under the WebRTC Code of Conduct - https://webrtc.org/support/code-of-conduct.
---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/b546e30b-9592-44c9-87ee-9faceca1fd36n%40googlegroups.com.