- From: guest271314 via GitHub <sysbot+gh@w3.org>
- Date: Fri, 22 Nov 2019 00:50:11 +0000
- To: public-webrtc-logs@w3.org
> Do web authors find semantic value in using `track.enabled` as the API meant to successfully implement `mute/unmute` in all browsers? In a way that turns off the hardware light? wo/prompt? Sure, as long as the caveat is clearly explained that `track.enabled` relevant to _mute/unmute_ is only applicable to a `MediaStreamTrack` from `getUserMedia()` and not any derivative specifications which though discrete still refer and link to Media Capture and Streams specification (i.e., `track.getSettings()` does not provide the same output for `HTMLMediaElement.captureStream()` or `canvas.captureStream()`). > Will end-users be able to temporarily turn off/on their camera/mic in conference calls without a prompt in all browsers? Remains to be seen. > Will indicators give them confidence they're not being watched? Depends on whom is asked. There is no expectation of privacy for any signal communications. -- GitHub Notification of comment by guest271314 Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/642#issuecomment-557338376 using your GitHub account
Received on Friday, 22 November 2019 00:50:13 UTC