- From: Harald Alvestrand via GitHub <noreply@w3.org>
- Date: Tue, 28 Oct 2025 12:48:45 +0000
- To: public-webrtc-logs@w3.org
While those interfaces are not Web-exposed, it seems just make-work to me to add language saying "these algorithms work on objects that for all intents and purposes are excatly the same as RTCEncodedAudioFrame and RTCEncodedVideoFrame". (Note - the transform algorithm refers to the ability to run on a BufferSource, but the only reference to it is from a place that says that it passes a frame. So it's not clear that this third alternative can ever be exercised.) -- GitHub Notification of comment by alvestrand Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/issues/286#issuecomment-3456311351 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 28 October 2025 12:48:46 UTC