- From: Michał Śledź via GitHub <sysbot+gh@w3.org>
- Date: Wed, 17 Jan 2024 22:22:16 +0000
- To: public-webrtc-logs@w3.org
> That seems to be the reasonable consequence if you offer a set of codecs not supported? What exactly? > I'm somewhat concerned Edge M120 throws an error on the fiddle but that seems to be resolved in Edge Canary either by virtue of "go AV1" or because of [this commit](https://chromiumdash.appspot.com/commit/601ac2eea89a496ff32923aab0666376464eba8b) Thanks! We have very similar test in our Elixir implementation except that we also ensure that transceivers are removed ([link](https://github.com/elixir-webrtc/ex_webrtc/pull/61/files#diff-5fea3b7f22143f978ec01781ed41d00d204d6d9082129effb36f767594132b67R905)) -- GitHub Notification of comment by mickel8 Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2927#issuecomment-1897123945 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 17 January 2024 22:22:18 UTC