Re: [webrtc-pc] Unimplementable input validation steps in setCodecPreferences (#2805)

We need to define what it means to be "in" the array. Is it enough for the `payloadType` and `mimeType` to match? Or do all members including `clockRate`, `channels` and `sdpFmtpLine` (and whatever extension specs define in the future) also need to match? Probably the latter. Whatever the answer, we need to specify what it is.

GitHub Notification of comment by jan-ivar
Please view or discuss this issue at using your GitHub account

Sent via github-notify-ml as configured in

Received on Tuesday, 6 December 2022 01:08:09 UTC