murrine-radiocheck color issue

[BlueJ774]

Binary package hint: human-theme

I'm noticing this for the first time in lucid.

If you look at a check box in a dialog or on a web page, it looks fine. By default, the bgcolor is selected_bg_color and the check or radio dot looks white until moused over and it looks black. However, if you look in a drop-down menu that has checks or radio dots, they are white both when moused over and not. This causes a problem. It's very difficult to see the checks and dots when not moused over because they are white on gray.

If you look into the gtkrc files for the human-theme themes, you'll find this section:
style "murrine-radiocheck"
{
 text[NORMAL] = @selected_fg_color
 text[PRELIGHT] = @selected_fg_color
 bg[SELECTED] = @selected_bg_color # HACK: override button selection colour
}

At first, I though I solved the problem by commenting out the text[NORMAL] line.
#text[NORMAL] = @selected_fg_color

This did solve the menu drop-down issue. However, I soon discovered it created an issue with regular radio buttons and check boxes. They were now black instead of white by default. The black against the dark brown color that is the default for human-themes caused the check/dot to barely be visible.

Next, I commented out the bg[SELECTED] line.
#bg[SELECTED] = @selected_bg_color # HACK: override button selection colour

This lightened the brown color in the background of checked check boxes and radio dots to a usable state. It works, but it's hardly ideal.

Ideally, I'd expect checks/dots in drop-down menus to be black by default and white when moused over. I'd expect regular check boxes and radio dots to be white normally and black when moused over.

I don't know that murrine currently allows a way to switch by context like that. I was unable to find any substantial documentation on the murrine engine. Otherwise, I would attempt a fix myself.

[Vish (vish)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 553393, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.