Community
Participate
Working Groups
I'm running Fedora 14. When the stack loses focus, the trim becomes very plain and the tab feels underdecorated to me. I like the light border on the unfocused stack, but the border around the top item's tab and the background colour of the tool items (Bug 372539) makes for an abrupt change. I'll attach a screenshot.
Created attachment 211608 [details] Unfocused view stack I really like the light trim, right up to the point where it meets the tab border in the top-left. The switch from no line to line makes the stack look odd. Maybe a lighter border all around will do the trick... (FWIW, I'm not *just* complaining, I'll see if I can hack together some alternatives).
Created attachment 211618 [details] Inactive stack with keyline specified Just adding trim to the basic stack make it look better. Here are the changes to the CSS: .MPartStack { ... outer-keyline-color: #B4B4B4; } .MPartStack.active { unselected-tabs-color: #DCDCDC #E1E1E1 #FFFFFF 100% 100%; // outer-keyline-color: #B4B4B4; tab-outline: #B4B4B4; } i.e. don't change the outline-keyline-color when we go active. Just set it and keep it. Thoughts?
Created attachment 211849 [details] Unfocused tab treatment The initial idea was to keep it completely minimal and have no lines at all but that got some negative feedback in that it was hard to see what was last active in a stack. Our designer suggested this look for unfocused tabs. What do you think?
(In reply to comment #3) > Created attachment 211849 [details] > Unfocused tab treatment > > The initial idea was to keep it completely minimal and have no lines at all but > that got some negative feedback in that it was hard to see what was last active > in a stack. Our designer suggested this look for unfocused tabs. What do you > think? +1
(In reply to comment #3) +1. That could work.
I took a stab at this today - check it out in tonight's build. The final gradient should probably be controlled through CSS...
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. If the bug is still relevant, please remove the "stalebug" whiteboard tag.
