Closed Bug 998542 Opened 11 years ago Closed 11 years ago

Regression from bug 610545 - arrow panels not working on Linux

Categories

(Toolkit :: UI Widgets, defect)

x86_64
Linux
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 994562

People

(Reporter: stephen.moehle, Unassigned)

Details

Arrow panels (toolbar bookmark menu and downloads button list) do not show up when clicking on the associated button on the toolbar. The downloads list never shows, but the bookmark menu might show up once or twice at most and then never again. There is some flickering when clicking on the buttons. Mozregression tells me that this is a regression caused by bug 610545: The first bad revision is: changeset: 177557:e4f3408af361 user: Neil Deakin <neil@mozilla.com> date: Tue Apr 08 08:45:52 2014 -0400 summary: Bug 610545, arrow panels should animate when opening and when cancelling, r=neil,dao Regression found using mozcommitbuilder 0.4.10 on linux2 at 2014-04-18 23:41:56 And it was around the 9th that I first noticed this problem. This is happening on Fedora 20, 64-bit.
Blocks: 610545
Flags: firefox-backlog?
Flags: firefox-backlog? → firefox-backlog+
Whiteboard: p=0
Panels are not working for me on Linux. I had a couple of days where the new animating panels were working for me, but now they don't; so not sure if this is exactly the OP's problem. When I click say the Downloads toolbar button, I get a quick flicker of the panel and then it remains hidden.
Status: UNCONFIRMED → NEW
Ever confirmed: true
My mozregression run gave me this: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=878193cac6b7&tochange=c2c661f15fcd though I am pretty sure that I was running a nightly build at one point where the panels were working correctly.
Looks like a dup of bug 994562. Try running xcompmgr or another X compositor before starting Firefox to confirm dup.
No longer blocks: 610545
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
Flags: firefox-backlog+
Whiteboard: p=0
You need to log in before you can comment on or make changes to this bug.