Open
Bug 1641934
Opened 5 years ago
Updated 4 years ago
Adding a Drag Space during screen sharing makes the Customization panel unresponsive when tab switch warning is enabled
Categories
(Firefox :: Site Permissions, defect, P3)
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox77 | --- | affected |
People
(Reporter: cfat, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
2.00 MB,
image/gif
|
Details |
[Affected Versions]:
- Firefox 77 RC-build 3
[Affected Platforms]:
- Windows 10 x64
[Prerequisites]:
- Firefox 77 RC-build 3 is installed.
- The following preferences are set:
-> privacy.webrtc.allowSilencingNotifications = true
-> privacy.webrtc.legacyGlobalIndicator = false
-> privacy.webrtc.sharedTabWarning = true - Have at least 2 tabs opened.
[Steps to reproduce]:
- Open the browser with the profile from prerequisites.
- Start a webRTC video call on Zoom and share the entire screen.
- Right-click on tab strip and select the "Customize" option.
- Select the "Drag Space" checkbox.
- Click in the "Done" button and observe what happens next.
[Expected results]:
- The Customization panel is dismissed.
Actual results]:
- The Customization panel remains unresponsive.
[Notes]:
- This issue is only reproducible when sharing the entire screen or the meeting room.
- Attached is a .gif with the issue.
Comment 1•5 years ago
|
||
Are you able to reproduce this if privacy.webrtc.sharedTabWarning
is set to false
?
Flags: needinfo?(cfat)
Reporter | ||
Comment 2•5 years ago
|
||
- I was not able to reproduce the issue with privacy.webrtc.sharedTabWarning pref set to false.
- Tested on Windows 10 x64 with Firefox RC 77 (Build ID: 20200528194502) and Firefox Beta 78.0b2 (Build ID: 20200602134412)
Flags: needinfo?(cfat)
Updated•5 years ago
|
Summary: Adding a Drag Space during screen sharing makes the Customization panel unresponsive → Adding a Drag Space during screen sharing makes the Customization panel unresponsive when tab switch warning is enabled
Updated•5 years ago
|
Priority: -- → P3
Updated•4 years ago
|
Group: mozilla-employee-confidential
You need to log in
before you can comment on or make changes to this bug.
Description
•