Within the last few months (don't know exactly when) a new warning has started to appear that states when one sets the "background-color" to some color and sets "color" to "inherit":

"You have no color set (or color is set to transparent) but you have set a background-color."

In the past if I defined a background-color, as long as I also defined "color:inherit" the warning would go away (as it should). This is no longer the case, now even with color set to inherit I get the warning, which is really annoying.

If I set "color:inherit" when I define background-color I am implicitly setting a color and acknowledging that if one is defined the other must also be considered to prevent any conflicts, thus there should be no warning. It is up to me to make sure I don't cause a conflict in this case.

What makes this warning so annoying is that it generates so many unnecessary warnings that they can bury legitimate warnings that really do need to be looked at. Please revert back to the old behavior such that if background-color and color are set and one of them uses "inherit", don't generate a warning.

I try very hard to keep my pages error and warning free, however, in order to get rid of this warning I would have to increase the number of style rules and use inefficient selectors as using "inherit" currently allows me to define the color or background-color higher up and which can allow for different color/background-color depending on the context even if I explicitly define the other at a lower level.

Thanks,