- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Wed, 03 Jan 2024 14:21:16 +0000
- To: public-webrtc-logs@w3.org
> [@jan-ivar] Turning the question around: I would prefer a straight answer to my straight question. Exercises in turning questions around do not help us make progress, as this very thread demonstrates. Recall the question: > [@eladalon1983] When the mute event is fired and the app observes it and turns to handle it, what stats are available to it that would definitively, non-heuristically inform it that the track is muted due to an upstream entity such as the OS or UA? This question originally referred to Youenn's [preceding message](https://github.com/w3c/mediacapture-main/issues/982#issuecomment-1864600892). Ironically, it now also refers to Jan-Ivar's [message](https://github.com/w3c/mediacapture-main/issues/982#issuecomment-1864985520) which sought to brush the very question aside! In this message Jan-Ivar also suggested: > lack of frames in stats + !track.[muted](https://w3c.github.io/mediacapture-main/#dom-mediastreamtrack-muted) = malfunction The world is asynchronous. It is not possible to definitively correlate the presence/absence of recent frames with the presence/absence of recent mute events. Or if it is possible - please demonstrate how. This was the question. It warrants our attention. -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/982#issuecomment-1875446939 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 3 January 2024 14:21:18 UTC