Open Bug 1481242 Opened 6 years ago Updated 2 years ago

The "Page Actions" panel is misplaced after adding several buttons to the Address Bar

Categories

(Firefox :: Toolbars and Customization, defect, P3)

defect

Tracking

()

Tracking Status
firefox-esr60 --- affected
firefox61 --- wontfix
firefox62 --- fix-optional
firefox63 --- wontfix
firefox64 --- fix-optional

People

(Reporter: emilghitta, Unassigned)

References

Details

(Keywords: regression)

Attachments

(1 file)

Attached image Page Actions.gif
[Affected versions]:
63.0a1 (BuildId:20180806100140)
62.0b14 (BuildId:20180802174131)
61.0.1 (BuildId:20180704003137)
60.1.0esr (BuildId:20180621121604)

[Affected platforms]:
Windows 10 64bit.
macOS 10.9.5
Ubuntu 16.04 64bit.

[Steps to reproduce]:
1. Launch Firefox.
2. Access any webpage.
3. Click the "Page Actions" button.
4. Add several buttons to the Address Bar.

[Expected result]:
The panel's "pointer" is displayed under the "Page Actions" button.

[Actual result]:
The panel's pointer is displayed under the previously added buttons.

[Regression range]:
This seems to be a regression:

Last good revision: 2d815cb45cee4537af1e08c7ca8623c02c8a91b6
First bad revision: d8321357c4a7577860801e5fced1e2257ec428bf

Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=2d815cb45cee4537af1e08c7ca8623c02c8a91b6&tochange=d8321357c4a7577860801e5fced1e2257ec428bf

[Note]
This seems to be reproducible after adding at least 2 buttons to the Address Bar.
For further information regarding this issue please observe the attached screencast.
Hi Sam,

It seems that mozregression pointed out Bug 1412364 for causing this regression.

Can you please have a look into this?

Thanks!
Flags: needinfo?(sfoster)
Yeah I'll take a look. Its interesting that when the first button is added, the menu repositions, but not after the subsequent ones.
Assignee: nobody → sfoster
Flags: needinfo?(sfoster)
Too late for  61, but we could still take a patch for 63 and even potentially uplift for 62.
Priority: -- → P3
Too late to fix in 63, but we could still take a patch in 65 and potentially, 64 beta.
Assignee: sfoster → nobody
Severity: minor → S4
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: