- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Tue, 19 Dec 2023 14:02:21 +0000
- To: public-webrtc-logs@w3.org
It's in the [OP](https://github.com/w3c/mediacapture-main/issues/982#issue-2029404910): _"There can be several reasons for a [MediaStreamTrack](https://w3c.github.io/mediacapture-main/#dom-mediastreamtrack) to be muted: the user pushing a physical mute button on the microphone, the user closing a laptop lid with an embedded camera, the user toggling a control in the operating system, the user clicking a mute button in the [User Agent](https://w3c.github.io/mediacapture-main/#dfn-user-agent) chrome, the [User Agent](https://w3c.github.io/mediacapture-main/#dfn-user-agent) (on behalf of the user) mutes, etc."_ The _"etc."_ refers to other _"reasons"_ ... _"the [User Agent](https://w3c.github.io/mediacapture-main/#dfn-user-agent) initiates such a change"_, including _"access may get stolen ... in case of an incoming phone call on mobile OS"_. I dunno when Safari implemented its pause, but I think it was fairly early? But I don't understand why it matters since it's common and desirable for specs to exist before implementations. Specs define implementations. When I said _"most people"_ I meant outside of WebRTC. [Muting](https://www.google.com/search?q=muting) is a verb, a function. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/982#issuecomment-1862814862 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 19 December 2023 14:02:23 UTC