Re: [mediacapture-transform] How does generator.mute change track states? (#81)

> I think being conservative here means keeping some control over what JS can do in this new role

I think we're at a fundamental difference of opinion here.

You are arguing that we should insert behavior that is hard for the JS programmer to reason about and thus program to in the name of "conservatism".

I am arguing that given that the mechanism exists, and we're giving access to it at all, we should give JS programmers the simplest model to reason about, so that they can do what they think is the Right Thing without worrying about the UA inserting arbitrary restrictions to limit what they can do with it.

This UI does not prevent a lot of behaviors that could be considered unexpected, including:
- inserting frames of varying sizes
- inserting frames with timestamp changes that don't correspond to real time passing
- Inserting multiple frames in a single execution cycle

And so on and so forth.

Messing up people's mental model of what "mute a source" means ("mute all tracks, when tracks' muted state change they fire an event) because of a completely theoretical fear of the JS programmer might possibly do does not appear reasonable to me.


-- 
GitHub Notification of comment by alvestrand
Please view or discuss this issue at https://github.com/w3c/mediacapture-transform/issues/81#issuecomment-1056504612 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 2 March 2022 07:58:46 UTC