- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Mon, 28 Feb 2022 23:15:23 +0000
- To: public-webrtc-logs@w3.org
I don't understand the last argument. If I mute and unmute a track a thousand times, I expect to see a thousand mute events - not 999, not 1, not 0, but 1000. Anything else violates the principle of least astonishment. Also, this code: generator.muted = true; <stuff> generator.muted = false; <stuff> generator.muted = true; <stuff> generator.muted = false; will then have a number of events fired that depends on both the content of <stuff> and on the relative timing of the queued events. Again, violating the principle of least astonishment. If we change the prose to be: run the following steps: - For each live track sourced by this, queue a task to set a track’s muted state to [[IsMuted]]. we will get a totally predictable number of events. That seems desirable to me. (I agree with not changing the state of the track synchronously.) -- GitHub Notification of comment by alvestrand Please view or discuss this issue at https://github.com/w3c/mediacapture-transform/issues/81#issuecomment-1054799005 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 28 February 2022 23:15:25 UTC