Closed Bug 1145522 Opened 9 years ago Closed 9 years ago

Theme switcher panel and Show/hide menus in customization mode are mispositioned

Categories

(Firefox :: Toolbars and Customization, defect)

39 Branch
All
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1145868
Tracking Status
firefox38 --- unaffected

People

(Reporter: u428464, Unassigned)

References

Details

(Keywords: regression)

Since a few days on Nightly the theme switcher panel in customization mode doesn't anchor to the button anymore but far above. Same for the show/hide menu that appears in the middle of the screen.
Component: Theme → Toolbars and Customization
Sounds like it's caused by bug 1143974. :tn?
Blocks: 1143974
Flags: needinfo?(tnikkel)
[Tracking Requested - why for this release]:

Regression range:
good=2015-03-15
bad=2015-03-16
http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=af68c9c0e903&tochange=436686833af0

suspected: 
Timothy Nikkel — Bug 1130400. Part 1. Pass the passed in anchor frame to SetPopupPosition in nsMenuPopupFrame::LayoutPopup if we have one. r=enndeakin
Blocks: 1130400
No longer blocks: 1143974
Version: Trunk → 39 Branch
I'll investigate. If I can't fix it shortly I'll back out.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Hmm, so my local bisection blames https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?changeset=6cd4d71818ee

However applying part 2 of bug 1130400 fixes the bug for me. This does make sense since a change on reflow of flex items could determine if the condition of bug 1130400 comes up or not.

Part 2 of bug 1130400 is already on inbound, so this bug should get fixed when that merges.
(In reply to Timothy Nikkel (:tn) from comment #5)
> Hmm, so my local bisection blames
> https://hg.mozilla.org/integration/mozilla-inbound/
> pushloghtml?changeset=6cd4d71818ee


It was a speculative guess of mine, so maybe I was wrong.
Sorry dupe
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
No longer blocks: 1130400
Flags: needinfo?(tnikkel)
You need to log in before you can comment on or make changes to this bug.