After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 560796 - Rhythmbox opening and closing from notification tray is inconsistent
Rhythmbox opening and closing from notification tray is inconsistent
Status: RESOLVED DUPLICATE of bug 464304
Product: rhythmbox
Classification: Other
Component: User Interface
0.11.x
Other All
: Normal trivial
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-11-14 13:37 UTC by Hew McLachlan
Modified: 2008-11-14 21:31 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Hew McLachlan 2008-11-14 13:37:33 UTC
Please describe the problem:
When Rhythmbox is in the notification area, clicking to view it causes the window to be displayed using the open animation. However, clicking again to remove it from view causes it to use the minimise animation. This can easily be seen with Compiz animations. 

For consistency, it should use either the open/close or unminimise/minimise pair (GNOME might have a guideline on this), but not a combination of both. For reference, Pidgin uses open/close.

Steps to reproduce:
1. Open Rhythmbox in the notification area. Also use Compiz animations if possible for easy viewing.
2. Note that when opening the player (enabling Show Music Player), the open animation is used.
3. Note that when closing the player (disabling Show Music Player), the minimise animation is used.

Actual results:
The open and minimise animations are used.

Expected results:
Either the open and close animations, or the unminimise and minimise animations are used as a pair.

Does this happen every time?
Yes

Other information:
From https://bugs.launchpad.net/bugs/194628
Comment 1 Jonathan Matthew 2008-11-14 21:31:31 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 464304 ***