This issue is not intended to be a style issue,
but rather one of useability because of text illegibility.

At the heart of this issue is the assumption that it is okay
to specify either a "background-color" or "color" in module
CSS files without feeling the need to specify an accompanying
"color" or "background-color".

That mistaken assumption ignores the all too real possibility
that parent items can and do define the background-colors or colors
that will render text illegible when module CSS defines only one or the other
in a rule declaration.

This problem is Not limited to core modules; rest assured.

A core example...

Line 69 of modules/color/color.css

#palette .item-selected {
background: none repeat scroll 0 0 #EEEEEE;
}

For reasons of useability related to illegible text,
all modules should be required to specify both
"background-color" and "color" when one or the other
is desired to be specified in their CSS rule declarations.

Please notify the Queen; and the king, if he is around.
I am sure they will concur.

- The Prince of Darkness... Zen Midnight. :o)

CommentFileSizeAuthor
palette__.item-selected.jpg129.25 KBchristopher james francis rodgers

Comments

devin carlson’s picture

devin carlson commented
Status: Active » Closed (won't fix)

Although there could definitely be visibility issues related to having certain modules declaring a background color and others declaring a text color, I think that there are simply too many situations/combinations to make this a rule.

For example, if you are building an administration theme and you employ a number of modules to create form elements, each form element could have a different text color (declared by their respective modules). You would have to override each module CSS file or selector in order to make all text colors the same.

If there are specific issues where you see these visibility problems arise, I'd encourage you to open issues with each associated module.