+++ This bug was initially created as a clone of Bug #1693677 +++ ### Use case Lurkers in medium-to-large meetings who spend most of their time facemuted and micmuted, only to unmute when called on to ask some question. Don't prompt them for permission if they granted permission at the start of the meeting. *"Unmute"* here may refer to only faceunmute on some sites (Meet, WebEx), or both faceunmute and micunmute on others (MeetEcho?). This is because some web conferencing sites (the former group) asymmetrically stop camera on facemute to work around [crbug 642785](https://crbug.com/642785), but never stop the mic on micmute (so they can implement the "Are you speaking? you should unmute" feature). ### Proposal To address this use case directly, we might want to significantly increase the grace period considered in bug 1693677 to minutes not seconds, for as long as the page is not navigated (then trim it down to seconds on navigation). This could manifest as a second pref setting, and some conditional code on top of bug 1693677.
Bug 1697284 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
+++ This bug was initially created as a clone of Bug #1693677 +++ ### Use case Lurkers in medium-to-large meetings who spend most of their time facemuted and micmuted, only to unmute when called on to ask some question. They may lurk for nearly an hour to ask a question at the end. Don't prompt them for permission if they granted permission at the start of the meeting. *"Unmute"* here may refer to only faceunmute on some sites (Meet, WebEx), or both faceunmute and micunmute on others (MeetEcho?). This is because some web conferencing sites (the former group) asymmetrically stop camera on facemute to work around [crbug 642785](https://crbug.com/642785), but never stop the mic on micmute (so they can implement the "Are you speaking? you should unmute" feature). ### Proposal To address this use case directly, we might want to significantly increase the grace period considered in bug 1693677 to minutes not seconds, for as long as the page is not navigated (then trim it down to seconds on navigation). This could manifest as a second pref setting, and some conditional code on top of bug 1693677.
+++ This bug was initially created as a clone of Bug #1693677 +++ ### Use case Lurkers in medium-to-large meetings who spend most of their time facemuted and micmuted, only to unmute when called on to ask some question. They may lurk for nearly an hour to ask a question at the end. Don't prompt them for permission if they granted permission at the start of the meeting. *"Unmute"* here may refer to only faceunmute on some sites (Meet, WebEx), or both faceunmute and micunmute on others (MeetEcho?). This is because some web conferencing sites (the former group) asymmetrically stop camera on facemute to work around [crbug 642785](https://crbug.com/642785), but never stop the mic on micmute (so they can implement the *"Are you speaking? you should unmute"* feature). ### Proposal To address this use case directly, we might want to significantly increase the grace period considered in bug 1693677 to minutes not seconds, for as long as the page is not navigated (then trim it down to seconds on navigation). This could manifest as a second pref setting, and some conditional code on top of bug 1693677.