Closed Bug 1697304 Opened 4 years ago Closed 4 years ago

Drop-down corners are improperly displayed in low resolution

Categories

(Firefox :: Toolbars and Customization, defect)

Desktop
macOS
defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox-esr78 --- unaffected
firefox86 --- unaffected
firefox87 --- affected
firefox88 --- affected

People

(Reporter: danibodea, Unassigned)

Details

(Keywords: regressionwindow-wanted)

Attachments

(1 file)

Note

  • When the user sets the Dark Theme and clicks the "Hamburger Menu" button (or "Firefox Account" or "View history, saved bookmarks, and more" buttons), he will notice that the drop-down menu corners are badly displayed in low-resolution devices.

Affected versions

  • Nightly v88.0a1 - affected
  • Beta v87.0b7 - affected
  • Release v86.0 - unaffected
  • ESR v 78.8.0esr - unaffected

Affected platforms

  • reproducible on MacBook Air 2013; Mac OS 11.2; display aspect ratio of 16:10, resolution 1440x900.
  • not reproducible on MacMini 2011; Mac OS 10.13.6 (most probably) detects the compatible aspect ratio and resolution of the connected monitor; mine has 16x9 and resolution 1920 x 1080.

Steps to reproduce

  1. Lunch browser.
  2. Set the Dark Theme
  3. Click the Hamburger Menu button.

Expected result

  • The drop-down menu's corners are properly displayed in low resolution.

Actual result

  • The drop-down menu's corners are improperly displayed in low resolution.

Regression range

  • I could not investigate for the regressor because mozregression does not work on Mac OS 11.
  • It is highly possible this was introduced with Proton code.

Additional notes

  • This issue occurs with the drop-down menus opened by the "Show your history", "Show text encoding options", Tracking Protection, Site Information, "Page Actions", "Bookmark this page", "More tools..." and Hamburger Menu buttons.
  • When a Light Theme is enabled, the drop-down menu corners appear to have some kind of blur that makes it more aesthetic.
Severity: -- → S4
QA Whiteboard: [qa-regression-triage]

Is this reproducible with Proton disabled?

Flags: needinfo?(daniel.bodea)

Yes, considering the fact that I did not mention the activation of the feature, it most definitely did reproduce in build default, which is with Proton OFF (and also ON), but not on builds older than Proton. (Would have provided an exact change if mozregression worked on mac11)

Furthermore, this issue was found during a fast and hurried investigation of proton UI on small resolution screens:
https://docs.google.com/spreadsheets/d/1f5yhnI2O3uKSVJ_2iPa9bfSB_HRga8KY0KWBu7fCASM/edit#gid=0

Unfortunately, I spent too much time trying to reproduce it again on the latest and original builds and I could not reproduce it again. I do not know what caused it to reproduce in the first place. This having happened, I am noting to myself to put the exact build ID in every new bug from now on...

Considering the fact that it could not be reproduced again and no special settings were made to the MacBook I use, I will set this bug as WORKSFORME and keep my eyes peeled for a while. NI me for further info/testing.

Status: NEW → RESOLVED
Closed: 4 years ago
Flags: needinfo?(daniel.bodea)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: