- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Thu, 01 Dec 2022 09:37:44 +0000
- To: public-webrtc-logs@w3.org
Got it. Well setParameters() returns a promise, so if it cannot apply the parameters then the right thing to do is to reject that promise. If encoder errors happens later, then we have the same problem is no different from what it is today (you expect one codec, but you get a different one). If this is a real problem I think we could discuss an encoder error callback, but that is a separate issue. -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/126#issuecomment-1333484629 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 1 December 2022 09:37:46 UTC