Open Bug 1702438 Opened 8 months ago Updated 7 months ago

[Proton][macOS] The outline of the webRTC permission panel disappears upon switching the window from secondary monitor to main

Categories

(Firefox :: Site Permissions, defect, P3)

Desktop
macOS
defect

Tracking

()

Tracking Status
firefox87 --- disabled
firefox88 --- disabled
firefox89 --- affected

People

(Reporter: tbabos, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [proton-door-hangers])

Attachments

(2 files)

Attached image Screenshot of the issue

Tested on:
Nightly 89.0a1

Tested Platforms:
MacOS 10.15
Not reproducible on Windows

Have the following prefs enabled:
browser.proton.enabled (optional)
browser.proton.doorhangers.enabled (mandatory)
Light Theme
Secondary monitor connected. I have a 1920x1080 monitor connected to a MacBook Pro with 3072 x 1920 resolution. Reproduced this issue on another MacBook Pro connected to a different monitor as well. Reproduced it with a 2k monitor connected too.

Steps to reproduce:

  1. Open https://mozilla.github.io/webrtc-landing/gum_test.html
  2. Move the window to the secondary monitor and make sure it is maximized (not full screen)
  3. Click on the Camera or Microphone button
  4. Check the Permission Panel
  5. Grab the window and move it over to your main monitor (the one from the MacBook in my case)

Expected Results:
The permission panel should adapt to the resolution switch without affecting any visual elements.

Actual Results:
The outline of the webRTC permission panel disappears upon switching the window from the secondary monitor to the main one. Can't reproduce vice-versa.

Notes:
This is reproducible only behind the "browser.proton.doorhangers.enabled" pref. If I enabled only the global proton pref, it is not reproducible nor on non-proton builds.
Not visible (or reproducible) with Dark theme.

Priority: -- → P3
Attached image Beta.0b11

On the latest Firefox Beta 89.0b11, the outline will no longer disappear. However, the shadow of the permission panel will not be displayed anymore upon following the steps from Comment 0.

You need to log in before you can comment on or make changes to this bug.