261266 2023-09-07 02:32:56 -0700 WebRTC maintain-framerate degradationPreference does not apply to resolution adaptation 2024-02-09 06:32:36 -0800 1 1 1 Unclassified WebKit WebRTC WebKit Nightly Build All All RESOLVED FIXED https://bugs.webkit.org/show_bug.cgi?id=267577 BrowserCompat, InRadar P2 Normal --- 1 coin_st youennf coin_st kagh karlcow maojie0924 webkit-bug-importer youennf oldest_to_newest 1976085 0 coin_st 2023-09-07 02:32:56 -0700 By configuring video sender's degradationPreference as maintain-framerate according to standard (https://www.w3.org/TR/mst-content-hint/#degradation-preference-when-encoding), resolution adaptation is expected to be adaptive when certain limitation reasons are satisfied such as lack of compute resources or bandwidth. But safari does not work with this setting under any circumstance even at the beginning, sending resolution usually starts with lower dimensions then ramps up to the target resolution, chromium and firefox both work and we can observe this behavior under maintain-framerate. We set degradationPreference by following code snippet: s = pc.getSenders()[1]; p = s.getParameters(); p.degradationPreference = "maintain-framerate"; s.setParameters(p); Chromium and firefox will have distinct resolution adaptation at beginning and you may check getStats() outbound qualityLimitationReason which should be "bandwidth" and slow resolution ramp up can be observed, but nothing would happen on safari, plus seems qualityLimitationReason is not supported by safari. 1977466 1 webkit-bug-importer 2023-09-14 02:33:13 -0700 <rdar://problem/115481961> 1979786 2 youennf 2023-09-25 06:57:15 -0700 Pull request: https://github.com/WebKit/WebKit/pull/18155 1980114 3 ews-feeder 2023-09-26 02:38:28 -0700 Committed 268443@main (8bfbdfcad876): <https://commits.webkit.org/268443@main> Reviewed commits have been landed. Closing PR #18155 and removing active labels. 2000312 4 coin_st 2023-12-17 19:33:23 -0800 (In reply to youenn fablet from comment #2) > Pull request: https://github.com/WebKit/WebKit/pull/18155 Hi Youenn, do you know what target release that will have this fix? 2005239 5 youennf 2024-01-16 04:59:15 -0800 Follow-up fix needed at https://bugs.webkit.org/show_bug.cgi?id=267577. 2012174 6 kagh 2024-02-09 06:32:36 -0800 @youenn we have tested from our end and it works now. Thanks