- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Fri, 22 Nov 2019 10:58:29 +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? enabled is synchronous which makes it not straightforward to prompt on enabled value change. If we believe this is an important pattern, we should add a proper API for that. > Will end-users be able to temporarily turn off/on their camera/mic in conference calls without a prompt in all browsers? Will indicators give them confidence they're not being watched? Safari shows a browser UI to mute/unmute capture, this indicator is in sync with the hardware light and should give confidence for users. It is true that these indicators are not in sync with the page UI. This area is still evolving in browsers and its UI. I am not sure we are able to make a decision on the exact design. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/642#issuecomment-557488420 using your GitHub account
Received on Friday, 22 November 2019 10:58:31 UTC