Open Bug 1702146 Opened 6 months ago Updated 6 months ago

In private browsing the recently closed tabs/windows, clear history are not correctly aligned

Categories

(Firefox :: Menus, defect, P2)

defect

Tracking

()

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

People

(Reporter: raluca.popovici, Unassigned)

References

(Blocks 2 open bugs)

Details

(Whiteboard: [proton-hamburger-menu][priority:2c])

Attachments

(2 files)

Attached image 2021-03-31_08h26_27.png

[Affected versions]
Release 87
Beta 88
Nightly 89

[Affected platforms]
Win 10

[Precondition]
The following pref is set on true:

  • browser.proton.enabled

[Steps to reproduce]

  1. Open the Firefox browser
  2. Open 2 new windows and close them
  3. Reach the History submenu from the Hamburger menu
  4. Recently Closed windows is active and clickable
  5. Open a new private window
  6. Reach the History submenu from the Hamburger menu
  7. Close Private window
  8. Open again a new private window
  9. Reach again the History submenu from the Hamburger menu

Actual result:
The recently closed tabs/windows are aligned on the right side. Please see screenshots from normal window and private window.

Expected result:
In private browsing the recently closed tabs/windows, clear history should be aligned in the left side.

Attached image 2021-03-31_08h26_14.png
No longer depends on: 1702144
Severity: -- → S4
Summary: In private browsing the recently closed tabs/windows, clear history are not correctly aligned → Recently closed tabs and windows menu items are misaligned in a private window
Summary: Recently closed tabs and windows menu items are misaligned in a private window → In private browsing the recently closed tabs/windows, clear history are not correctly aligned

Romain, could please set the priority for this bug when you get a chance?
Thanks!

Flags: needinfo?(rtestard)
Flags: needinfo?(rtestard)
Priority: -- → P2
Whiteboard: [proton-hamburger-menu] → [proton-hamburger-menu][priority:2c]
You need to log in before you can comment on or make changes to this bug.