- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Thu, 01 Dec 2022 10:10:24 +0000
- To: public-webrtc-logs@w3.org
Providing all possible fallback combinations would require not just one argument to setParameters(), but N arguments for all possible combinations. E.g. when falling back to a different codec, you might not want the same number of active layers or scalability modes etc. I think fallback logic is out of scope for this issue, I filed #127, but in there I argue that it's better to provide a callback and let the app decide than to make this more complicated. -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/126#issuecomment-1333526072 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 10:10:26 UTC