Open Bug 1707892 Opened 3 years ago Updated 3 years ago

The full length of the Tracking Protection panel does not fit inside a ~720p or smaller vertical axis screen


(Firefox :: Protections UI, defect, P2)




Tracking Status
firefox-esr78 --- unaffected
firefox88 --- unaffected
firefox89 --- affected
firefox90 --- affected


(Reporter: danibodea, Unassigned)


(Blocks 2 open bugs)


(Whiteboard: [proton-door-hangers] [priority:2c])


  • When the user opens the browser on a small resolution/screen and opens the full-length Tracking Protections Panel, he will notice that it won't fit the screen.

Affected versions

  • Nightly v90.0a1
  • Beta v89.0b4
  • Release v88.0 (will fit in ~720p but not in 600p)
  • ESR v 78.8.0esr (will fit in ~720p but not in 600p)

Affected platforms

  • all

Steps to reproduce

  1. Lunch browser.
  2. Load any page.
  3. Click the Shield icon from the Address Bar. (Tracking Protection Panel)
  4. Make sure the full length of the Panel is displayed; Click the "circled i" icon from inside the panel to open the Tracking Protection general information drawer.

Expected result

  • The panel fits inside the screen.

Actual result

  • The bottom part of the panel spills out of the screen.

Regression range

  • This is an issue that appeared with the implementation of the Proton UI; With the old design, the panel would fit in 720p and spill in 600p (pixels on the vertical axis).

Additional notes

  • This issue was encountered during the Proton E2E testing on small screens (commonly used screen resolution: 1280 x 720).
  • Setting S3 since resolution still occupies a top 10 spot woprldwide.
Whiteboard: [proton-door-hangers]

The ETP panel had styling applied for MR1 but didn't get a full rework as there's open work streams around it outside of MR1 scope. I agree that this is an issue as a number of users are on small vertical height screens, however I don't believe it can be fixed for 89.

Priority: -- → P2
Whiteboard: [proton-door-hangers] → [proton-door-hangers] [priority:2c]
You need to log in before you can comment on or make changes to this bug.