- From: youennf via GitHub <noreply@w3.org>
- Date: Thu, 05 Jun 2025 09:58:19 +0000
- To: public-webrtc-logs@w3.org
From a user/web app perspective, it should be equivalent. From a spec perspective, I was initially thinking that where the check happens may not really matter. With MSTP, it actually does: either MSTP checks the muted slot or it asserts that the muted slot is false. Given there is a step to enqueue a task to call [MSTP maybeReadFrame](https://w3c.github.io/mediacapture-transform/#maybereadframe), I would tend to do a check there. Similarly to `onmute`, when `onended` fires, no frame should be delivered, but frames may be in transit. [MSTP maybeReadFrame](https://w3c.github.io/mediacapture-transform/#maybereadframe) should probably check the track ready state slot. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/1017#issuecomment-2943536379 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 5 June 2025 09:58:19 UTC