GNOME Bugzilla – Bug 442866
Static colors for treeview expanders
Last modified: 2008-09-30 17:48:12 UTC
With rhythmbox 0.11 you introduced a new treeview on the left sidebar, with expandable proprieties. The problem is that those expanders has a fixed "gray" color so the text inside them becomes unreadable Steps to reproduce: 1. Open theme manager and select a dark theme 2. open rhythmbox and see the sidebar
Created attachment 89174 [details] Screenshot this is a screenshot
Is this fixed in HEAD?
i have tested with a theme like your and i can read the text. For me this isn't a bug because if you use it with a light theme you can read all
@Giuseppe: it represent a bug because the UI has to be intependent from the kind of theme the user chose. It should be working with every theme as the user shouldn't have to change is theme because of an application.
@ Andrea Yes, i know, this is an accessybilty problem. anyone of the rhythmbox team have read this bug? boh
Yes, this is a bug. We should probably just drop the background color setting until we can figure out a good theme compliant way. It actually looks pretty good without a bg color since we also have indentation to indicate hierarchy.
I think it looks OK without a background colour in the group rows, but my initial impression is that a border around those rows would help.
Actually, that's what's being suggested in bug 441891 (maybe that's where I got the idea?). Perhaps we should close this as a duplicate.
This problem is still present now. The problem is that gnome-themes-extras will have a dark theme that to witch rhythmbox will be incompatible with. I suggest to _at least_ shade the base color instead the bg. But changing the widget would be better. Notice that the theme will be released with 2.20
*** Bug 495488 has been marked as a duplicate of this bug. ***
Created attachment 101322 [details] [review] first stab at fixing this Removes the background from the source group rows, adds separators between source groups. It doesn't quite look right to me.
The patch in bug 553984 has already been committed, and should fix this problem.