- From: Dominique Hazael-Massieux via GitHub <sysbot+gh@w3.org>
- Date: Mon, 16 May 2022 11:40:41 +0000
- To: public-webrtc-logs@w3.org
the process we've agreed to move features from -extensions to -pc is https://github.com/w3c/webrtc-charter/blob/gh-pages/merge-guide.md which reads > to be considered for integration, a new extension must have: > * Reasonable test coverage > * Two passing implementation From what I gather, this is actually now implemented in [Chromium](https://chromestatus.com/feature/6216116758118400), [Firefox](https://bugzilla.mozilla.org/show_bug.cgi?id=1611957) and Safari The [WPT test results](https://wpt.fyi/results/webrtc-extensions/RTCRtpParameters-maxFramerate.html?label=master&label=experimental&aligned&q=%2Fwebrtc-extensions%2FRTCRtpParameters-maxFramerate.html) don't really reflect this show (all fail on firefox, 2 fail on Safari), although I'm not sure how concerning these failures are from an interop perspective. More concerning is the report in https://bugzilla.mozilla.org/show_bug.cgi?id=1611957 that the spec'd behavior is incompatible with libwebrtc IIUC. So it looks like after a bit of WPT work, this should be mostly ready to merge in the main spec -- GitHub Notification of comment by dontcallmedom Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/108#issuecomment-1127565124 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 16 May 2022 11:40:42 UTC