Open Bug 1781918 Opened 3 years ago Updated 11 months ago

Jitsi camera picker's gallery view popup of cameras triggers Firefox's per-device permission

Categories

(Core :: WebRTC: Audio/Video, defect, P3)

x86_64
Linux
defect

Tracking

()

Tracking Status
firefox105 --- affected

People

(Reporter: jib, Unassigned)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

Attached image JitsiPicker.png

This issue is tracking a poor UX situation where Jitsi triggers Firefox's per-device permission prompts prematurely. Galleries are great, though some users may balk at turning on all cameras.

From bug 1780730 comment 3:

Jitsi allows the user to open a dropdown with both live video input streams, so he can select one or the other. In a normal situation, a firefox user has only allowed one of them when he joined the call, so when he opens the drop-down, another permission door hanger is triggered, for the other webcam that is already connected to the system. If the user allows this second video input permission door-hanger, then closes and reopens Jitsi's stream selection drop-down, both streams are properly working and can be correctly switched.

STRs:

  1. Have two or more cameras, e.g. "FaceTime HD Camera (Built-in)" and "Logitech BRIO". (revoke any existing permission to them first)
  2. Add a new meeting at https://meet.jit.si/ and allow it camera ("FaceTime HD Camera (Built-in)" to start)
  3. "Join" the meeting
  4. Click the ^ button next to the 📹 camera toggle button.

Expected results:

  • A popup gallery of two choices "FaceTime HD Camera (Built-in)" and "Logitech BRIO", the former with live preview, the latter without, both selectable.

Actual results:

  • The second choice has no name and is unselectable. A Firefox permission prompt is asking for permission to "Logitech BRIO". Preview never appears and choice remains unselectable even after grant

Workaround:

  • grant permission, then close popup with ^ and reopen it
No longer depends on: 1780730

I think if we fixed bug 1609427 then Jitsi could solve this.

Depends on: 1609427

The severity field is not set for this bug.
:jib, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(jib)
Severity: -- → S3
Flags: needinfo?(jib)
Priority: -- → P3
Blocks: jitsi
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: