- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Wed, 02 Oct 2024 09:49:31 +0000
- To: public-webrtc-logs@w3.org
Laundry list: - Update the normative text [here](https://w3c.github.io/webrtc-pc/#dom-rtcrtptransceiver-setcodecpreferences) to clarify this is not _just_ "default receive codec preferences" (e.g. can also be used to set send codec preferences on a sendonly transceiver and so on). - Update [algorithm](https://w3c.github.io/webrtc-pc/#dom-rtcrtptransceiver-setcodecpreferences) to allow both send codecs and receive codecs (currently it says to throw InvalidModificationError in the sendonly use case). - The [final steps to create an offer](https://w3c.github.io/webrtc-pc/#dfn-final-steps-to-create-an-offer) and [answer](https://w3c.github.io/webrtc-pc/#dfn-final-steps-to-create-an-answer)'s directionality filtering is actually correct already, however we need to clarify/decide what to do when preferences become empty due to filtering. - The [setParameters algorithm](https://w3c.github.io/webrtc-pc/#dom-rtcrtpsender-setparameters) is as far as I can tell correct, no action needed. -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/3006#issuecomment-2388137592 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 2 October 2024 09:49:32 UTC