- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Wed, 26 Mar 2025 20:51:00 +0000
- To: public-webrtc-logs@w3.org
> This change would allow you to say (ahead of negotiation) that "I want codecs VP8, VP9 and AV1, and have a simulcast with layer 1 sending H.264". This seems somewhat unlikely to be consistent; do we negotiate H.264 support at all when H.264 is not in the preference list? We don't. VP8, VP9 and AV1 (or some subset) will be negotiated and the H.264 codec parameter will be [removed](https://w3c.github.io/webrtc-pc/#ref-for-dom-rtcrtpencodingparameters-codec-2) once "stable". This works as intended. This logic removed by this PR introduced temporal coupling, where two operations are valid only if performed in a particular sequence. Websites might set preferred codecs and codec parameters in any order ahead of negotiation. Luckily, I seem unable to provoke `InvalidModificationError` in Chrome using https://jsfiddle.net/jib1/gxwrz9ko/ regardless of what order set things in. So this PR appears to align spec with implementation. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/webrtc-pc/pull/2991#issuecomment-2755718757 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 26 March 2025 20:51:01 UTC