- From: Philipp Hancke via GitHub <sysbot+gh@w3.org>
- Date: Mon, 05 Dec 2022 20:41:29 +0000
- To: public-webrtc-logs@w3.org
setParameters is the wrong mindset. setCodecPreferences is more similar. We have a *major* problem of not being able to ship things that are not suitable to be enabled by default because they do not apply most of the time. setOfferedRtpHeaderExtensions solves this by providing an API to say "oh you support this? I want it". I do not think there is a web-compat issue here since SDP O/A (which is *not web*) will take care of this. -- GitHub Notification of comment by fippo Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/130#issuecomment-1338137429 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 5 December 2022 20:41:31 UTC