When I compare the panel animations in Nightly on Mac and on any of my Windows VMs, the Mac version is noticeably less smooth, even though Windows is slowed down by running inside a VM. I wonder if we can achieve the same performance on Mac as we have on Windows.
The panel shadow can probably be blamed for this, at least partly. On Mac we don't hardware accelerate panels (windows of type "popup") because their shadow is shaped around the panel content, and if we use OpenGL to render the window contents we lose the dynamic shaping ability. But this is only the case if the window server draws the shadow - if we instead set -moz-window-shadow:none; and drew our own shadow (with box-shadow, for example), we could enable hardware acceleration for the panel and the animation should be much smoother.
This has gotten quite a bit worse with Yosemite. Now the animations aren't just slower, the panel shadow appears first without any animation and then the panel expands. Plus, there's often a »blink« at the end of the transition where the panel disappears for a split second (but not the shadow) and then reappears. Markus, how do you see the chances of this getting attention? Apple is usually pretty fast in converting their user base to new OS versions.
Yeah, it really does look hideous on Yosemite. I'll check what happens if we do our own drop shadow drawing and use GL acceleration for the panels, when I have time.
Assignee: nobody → mstange
(Marking it as assigned, so that I can filter on unassigned bugs a little easier. ;)
Status: NEW → ASSIGNED
Hm, this got even worse in the last few Nightlies. I now only get about 2-3 frames of animation for panel opening. Sometimes there's no animation at all. Older versions of Firefox are slightly smoother. Markus, how is this doing priority-wise at the moment?
Assignee: mstange → jaws
Assignee: jaws → nobody
Status: ASSIGNED → NEW
2 years ago
Do you still see this issue, phlsa?
Nope! It seems to be fixed now!
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.