- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Wed, 09 Mar 2022 20:37:39 +0000
- To: public-webrtc-logs@w3.org
> The UA can detect this and mute the tracks using any logic it wants (asynchronously if it so prefers). I agree with @guidou that muting [_as a model_](https://w3c.github.io/mediacapture-main/#life-cycle-and-media-flow) is something mediacapture-main defines — and that's as something happening asynchronously [in the background](https://html.spec.whatwg.org/multipage/infrastructure.html#in-parallel) — and that we need to respect that model here. I agree with @alvestrand we can't leave it unspecified, because it's JS observable (but I disagree about what's POLA). Web developers expecting synchronous actions to influence asynchronous operations a certain way should take [this twitter poll](https://twitter.com/jaffathecake/status/1501100570421170183), which highlights that any assumptions they make about synchronous and asynchronous interactions are bad ones. Applying that to our case: I don't see why it matters what the net muted state is "[halfway through a JS call](https://twitter.com/jaffathecake/status/1501503446863728641)" (my new favorite phrasing of run-to-completion semantics). -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-transform/issues/81#issuecomment-1063348480 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 9 March 2022 20:37:40 UTC