Open
Bug 1647441
Opened 4 years ago
Updated 4 years ago
The screen-share permission door-hanger has a drop-down button without fixed visual boundaries on Linux and MacOS
Categories
(Firefox :: Site Permissions, defect, P3)
Tracking
()
People
(Reporter: danibodea, Unassigned)
References
(Blocks 2 open bugs)
Details
Attachments
(1 file)
447.17 KB,
image/jpeg
|
Details |
Note
- When the user clicks a WebRTC web-app's screen-share start button, the screen-share permission door-hanger is displayed and the drop-down button area is not properly shown. The drop-down button is missing a parting line on the right of the arrow, just like it has one on its left.
Affected versions
- Nightly v79.0a1
- Beta v78.0b9
- Release v77.0.1
Affected platforms
- This issue does not occur on the Windows platform because the "Allow" button is on the left and the"Not Now"+"Never Allow" buttons are on the right side of the door-hanger.
- This issue DOES occur on Linux and Mac OS
Preconditions
- Se the following precondidions:
- privacy.webrtc.allowSilencingNotifications = true
- privacy.webrtc.legacyGlobalIndicator = false
Steps to reproduce
- Engage in a WebRTC conference.
- Allow the microphone and camera permission door-hangers.
- Click on the web-apps's button to start screen sharing.
Expected result
- The door-hanger's buttons are properly delimited.
Actual result
- The "down arrow" button has a parting line on the left, but not in the right.
Regression range
- This issue only occurs after the newly implemented design of the screen-sharing permission door-hanger in FX77.
Additional notes
- Please note that this implementation works properly on Windows, so a fix may break the behavior on the Windows platform.
Updated•4 years ago
|
Priority: -- → P3
Updated•4 years ago
|
status-firefox-esr68:
disabled → ---
Reporter | ||
Updated•4 years ago
|
Reporter | ||
Comment 1•4 years ago
|
||
I'm not sure whether this bug can be considered valid or if it is fixable in any way, but it still reproduces just the same.
status-firefox81:
--- → affected
status-firefox82:
--- → affected
status-firefox83:
--- → affected
status-firefox84:
--- → affected
You need to log in
before you can comment on or make changes to this bug.
Description
•