Its a common validation check (if an annoying one) for CSS validators to report a warning if you set a foreground color without setting a background color. In general, its best to set both at some point. It eliminates ambiguity.

A user who specifies there own style sheet (are they any?) would have control over this sort of thing regardless of whether or not you set a background color on the body or not.

On 8-Nov-08, at 11:35 AM, Mohit Sindhwani wrote:

john wrote:
My assertion was that anyone who has gone to the effort of changing the browsers background color is well prepared to deal with the mess they make if they choose black for instance, i.e. those same people are also likely to have user level css applied in addition to deal with when this happens. I think this just happens to be one of his pet issues.

http://www.zeldman.com/2007/06/18/bgcolor-follies/
http://www.zeldman.com/2008/11/07/is-your-websites-underwear-showing/

Actually, I am tempted to agree with Saša on this one - if *you* set a foreground color, *you* should set a background color. A default background should not apply if you override the foreground.

I think Saša / Zeldman are talking about using a "default background" from the browser - on the other hand, if the user sets his browser to overwrite the colors specified by the page, then both the background and foreground colors are affected. Also (as John said), the user has clearly chosen to see it differently.

Cheers,
Mohit.
11/9/2008 | 3:35 AM.


_______________________________________________
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

_______________________________________________
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Reply via email to