- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Wed, 02 Mar 2022 11:17:04 +0000
- To: public-webrtc-logs@w3.org
I don't think we can leave it as implementation defined. It's a specified API, and specified APIs should have specified consequences, unless we have strong reasons not to. I think we have consensus that the muting of tracks shouldn't be synchronous (because event firing is a synchronous operation, and that would put user JS inside the mute-a-generator processing steps - bad idea). I also think that we haven't surfaced any reason that the "mute a track" operation defined in the mediacapture-main spec needs to change. The discussion is all about when and how to call it. -- GitHub Notification of comment by alvestrand Please view or discuss this issue at https://github.com/w3c/mediacapture-transform/issues/81#issuecomment-1056808880 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 11:17:05 UTC