Edit history

Earlier versions of Hide popout when no screenshare/camera enabled, newest first.

Current version | Edited by Rex
Changes
...Allowing for any combination of those, or blanket "all the time"/"never" options.Removed: ### ChecksRemoved: Removed: - ☑ I searched for existing issues and didn't find a duplicate.Removed:
Show

Hide popout when no screenshare/camera enabled

Problem

image image Right now, you can only pick to have the voice channel popout on or off, with no regard for what is currently happening in the channel.

Proposed solution

You should be able to select individual options for when the popout should show:
  • When someone has webcam on
  • When I am watching a screenshare
...Allowing for any combination of those, or blanket "all the time"/"never" options.
Edited by Rex
Changes
...Allowing for any combination of those, or blanket "all the time"/"never" options.Removed: ### Notes (optional)Removed: Removed: _No response_Removed: ### Checks
Show

Hide popout when no screenshare/camera enabled

Problem

image image Right now, you can only pick to have the voice channel popout on or off, with no regard for what is currently happening in the channel.

Proposed solution

You should be able to select individual options for when the popout should show:
  • When someone has webcam on
  • When I am watching a screenshare
...Allowing for any combination of those, or blanket "all the time"/"never" options.

Checks

  • ☑ I searched for existing issues and didn't find a duplicate.
Original by Rex
Show

Hide popout when no screenshare/camera enabled

Problem

image image Right now, you can only pick to have the voice channel popout on or off, with no regard for what is currently happening in the channel.

Proposed solution

You should be able to select individual options for when the popout should show:
  • When someone has webcam on
  • When I am watching a screenshare
...Allowing for any combination of those, or blanket "all the time"/"never" options.

Notes (optional)

No response

Checks

  • ☑ I searched for existing issues and didn't find a duplicate.