Ron Koster wrote:

> I've got the CSS for one of my sites validating with no errors, 
> except for the styling of the scrollbars (for IE only, of course), 
> i.e. "scrollbar-track-color", "scrollbar-face-color", etc. -- 
> this/these alone are causing the CSS file to not validate. In 
> searching the list archives, it would seem that there's nothing that 
> one can do about that, that using that "feature" simply will prevent 
> the CSS file from validating.

1: scrollbar styles affect a few non-IE browsers too. I never use IE for
surfing, but I see your colored scrollbars in my non-IE browser because
I've allowed it to act on those styles.

2: that proprietary stuff doesn't validate is as expected, and does not
invalidate the regular styles. So if you're sure the styles are ok and
work as intended, then there no real harm done.

If "total validity" matters and you want to keep the proprietary styles,
Conditionally Commented stylesheets for IE only stuff is an option.
This approach doesn't make the styles valid, but for most "hidden" is
good enough. Besides: the stuff will not show up in non-IE browsers when
CCs are used, which I personally think is more important.

> "You have no background-color set (or background-color is set to 
> transparent) but you have set a color. Make sure that cascading of 
> colors keeps the text reasonably legible."
> 
> How on earth is that a "warning"? If I set a background color for my 
> links or whatever else, well, then there goes my background graphic 
> out the window.

Background-color is layered behind background-image, so normally setting
a background-color as fallback shouldn't be a problem.

The shape / transparency of the background-images you're using may force
you to declare an actual background-color further back, and since the
validator can't see your visual design it can't clear you on that point
- hence the warning.

> On the other hands, are warnings like the above safe to just totally 
> ignore completely?

Warnings should not be ignored, as what they're usually pointing at is
something that may conditionally fail at the visitors' end. The
validator can't check all "what happens if", so it simply tells _you_ to
perform such checking. Only when you have manually checked and are sure
failures can not occur, can you safely ignore these warnings.

regards
        Georg
-- 
http://www.gunlaug.no
______________________________________________________________________
css-discuss [cs...@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/

Reply via email to