Closed (fixed)
Project:
Tray
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
26 Nov 2010 at 05:44 UTC
Updated:
8 Feb 2011 at 22:53 UTC
Hi.
In further testing and use of the tray, I found a few other issues.
If you click on an entry in the tray to open its block, then click again to close it, the .tray-item-active class is not removed.
This also applies to the minimise button.
Finally, clicking 'close' invokes fadeOut rather than slideToggle, inconsistently.
The attached patch corrects all of these issues.
| Comment | File | Size | Author |
|---|---|---|---|
| tray-click.patch | 1.32 KB | nigelcunningham |
Comments
Comment #1
shadcn commentedActually, it is meant to work like this. when you minimize an item, it is still active (selected). Unless you close an item or select another one, the item remains active.
Also, we've used a fadeout instead of slideToggle to differentiate between a minimize action and a close action.
Comment #2
nigelcunningham commentedIs there some difference between minimise and close that I've missed?
Thanks for the reply!
Nigel
Comment #3
shadcn commentedWhen you minimise an item, the item is still active (still selected) and you see the SlideDown effect. When you close an item (fadeOut), it loses the active class and is no more selected. (Think Windows and Gnome - its built to work like these)
Comment #4
shadcn commented