It really depends of the flow and API shape we expose, let's assume the following: 1. If camera is shuttered, track is muted. 2. UA exposes the `requestUnmute` method we talked about (it might be good to make progress there). Let's say that a web page is capturing but the camera track is muted. The user clicks on the unmute button in the web page which calls `requestUnmute`. In that particular case, the UA could tell the user what to do to unmute the track (unshutter the camera or provide appropriate information for that particular user setup). I am not sure it is always best to expose muted reasons given they are open ended and/or OS specific. It might make it hard for web pages to handle all cases/all platforms properly. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/930#issuecomment-1422837661 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-configReceived on Wednesday, 8 February 2023 15:50:45 UTC
This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:20:00 UTC