Sent by Gunlaug_Sørtun on 20 September 2005 21:09
Tanya Renne wrote:
> Can someone give me some insight around the warnings I get when
> validating css? How seriously should they be taken? Is the goal to
> have no errors and no warnings? What is the impact of different
> warnings?
A warning basically tells you that a particular part of your code is
perfectly valid, but that it _may_ give unwanted side-effects. The
validator can't check the end-result, so it's telling you to check your
choices one more time and make sure you made the right ones.
Examples:
- You may get a warning that some CSS3 code won't work reliable -- yet.
The validator can't check if you have coded fall-backs. Progressive
coding may give you a few of those.
- Warnings about (lack of) foreground/background colors tell you to
check that your choices are good. The validator can't see the
end-result, so things may work out perfectly well even with a few of those.
----
It is no goal to get zero warnings. It is a goal to check out and
understand why you get each one of them.
Well-calculated but non-valid code may be the only option in some rare
cases, so even a _very_ limited number of errors _may_ be acceptable if
you know exactly what you are doing.
regards
Georg
--
http://www.gunlaug.no
______________________________________________________________________
css-discuss [EMAIL-REMOVED]]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
