I have questions: 1. Is there a UX mock showing the buttons in muted state? Users will need to decode the four states. 2. If I mute, and then open a new tab that asks for cam/mic, will the new stream start muted? 3. If I mute, then close the tab (indicators disappear), then open a new tab that asks for cam/mic, will the new stream start muted (and will the indicators reappear muted)? 4. If I mute, then the site decides to stop the camera (indicators disappear), and then the site asks for cam/mic anew, will the new stream start muted? It's a global indicator that trumps site controls, yet whose appearance is controlled by the site? #4 is a trick question, because that's what Google Meet does to mute camera. If we go forward with this it will further reveal differences between sites: * Most sites, like whereby.com, use `track.enabled == false` to mute camera and microphone (red→gray Firefox indicator) * Google Meet however, uses `track.stop()` to mute camera—but not mic!—and then call `getUserMedia` again to unmute, because that's the only way to remove the camera hardware light on mute in Chrome (we're [pushing on Chrome](https://bugs.chromium.org/p/chromium/issues/detail?id=642785#c13) to [work like firefox](https://blog.mozilla.org/webrtc/better-privacy-on-camera-mute-in-firefox-60/) to avoid annoying Firefox permission re-prompts on unmute). This difference is observable today (see screenshot): In Meet the global camera indicator goes away on camera mute, whereas the microphone one doesn't go away on mic mute. Here's #4 again applied to Google Meet: 1. I'm in Google Meet with camera and microphone shared 2. I mute camera using the Firefox mute indicator 3. I mute camera using Meet's mute indicator (causes Firefox indicator to go away) 4. I unmute camera using Meet mute indicator (causes Firefox indicator to reappear) 5. Am I muted?
Bug 1643027 Comment 14 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I have questions: 1. Is there a UX mock showing the buttons in muted state? Users will need to decode the four states. 2. If I mute, and then open a new tab that asks for cam/mic, will the new stream start muted? 3. If I mute, then close the tab (indicators disappear), then open a new tab that asks for cam/mic, will the new stream start muted (and will the indicators reappear muted)? 4. If I mute, then the site decides to stop the camera (indicators disappear), and then the site asks for cam/mic anew, will the new stream start muted? It's a global indicator that trumps site controls, yet whose appearance is controlled by the site? #4 is a trick question, because that's what Google Meet does to mute camera. If we go forward with this it will further reveal differences between sites: * Most sites, like whereby.com, use `track.enabled == false` to mute camera and microphone (red→gray Firefox indicator) * Google Meet however, uses `track.stop()` to mute camera—but not mic!—and then calls `getUserMedia` again to unmute, because that's the only way to remove the camera hardware light on mute in Chrome (we're [pushing on Chrome](https://bugs.chromium.org/p/chromium/issues/detail?id=642785#c13) to [work like firefox](https://blog.mozilla.org/webrtc/better-privacy-on-camera-mute-in-firefox-60/) to avoid annoying Firefox permission re-prompts on unmute). This difference is observable today (see screenshot): In Meet the global camera indicator goes away on camera mute, whereas the microphone one doesn't go away on mic mute. Here's #4 again applied to Google Meet: 1. I'm in Google Meet with camera and microphone shared 2. I mute camera using the Firefox mute indicator 3. I mute camera using Meet's mute indicator (causes Firefox indicator to go away) 4. I unmute camera using Meet mute indicator (causes Firefox indicator to reappear) 5. Am I muted?
I have questions: 1. Is there a UX mock showing the buttons in muted state? Users will need to decode the four states. 2. If I mute, and then open a new tab that asks for cam/mic, will the new stream start muted? 3. If I mute, then close the tab (indicators disappear), then open a new tab that asks for cam/mic, will the new stream start muted (and will the indicators reappear muted)? 4. If I mute, then the site decides to stop the camera (indicators disappear), and then the site asks for cam/mic anew, will the new stream start muted? It's a global indicator that trumps site controls, yet whose appearance is controlled by the site? #4 is a trick question, because that's what Google Meet does to mute camera. If we go forward with this it will further reveal differences between sites: * Most sites, like whereby.com, use `track.enabled == false` to mute camera and microphone (red→gray Firefox indicator) * Google Meet however, uses `track.stop()` to mute camera—but not mic!—and then calls `getUserMedia` again to unmute, because that's the only way to remove the camera hardware light on mute in Chrome (we're [pushing on Chrome](https://bugs.chromium.org/p/chromium/issues/detail?id=642785#c13) to [work like firefox](https://blog.mozilla.org/webrtc/better-privacy-on-camera-mute-in-firefox-60/) to avoid annoying Firefox permission re-prompts on unmute in Meet). This difference is observable today (see screenshot): In Meet the global camera indicator goes away on camera mute, whereas the microphone one doesn't go away on mic mute. Here's #4 again applied to Google Meet: 1. I'm in Google Meet with camera and microphone shared 2. I mute camera using the Firefox mute indicator 3. I mute camera using Meet's mute indicator (causes Firefox indicator to go away) 4. I unmute camera using Meet mute indicator (causes Firefox indicator to reappear) 5. Am I muted?