This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
From http://jigsaw.w3.org/css-validator/BUGS.html From http://lists.w3.org/Archives/Public/www-validator-css/2001Aug/0072.html '' Alan J. Flavell argued, that the Validator should also complain 'background- color: transparent' as if background-color has been omitted ''
Fixed, see http://qa-dev.w3.org:8001/
This warning should not be applied. Many websites use background-image for backgrounds on their web pages. Thus the background color on links and "H" tags and "HR" tags in CSS MUST be "transparent". I have test numerous pages of my website against the validator and it comes up with warnings on all of my "H", "hr", and "a" tags. The additional comment below from Yves Lafon which shows a "fixed" validator works perfectly. Why is it NOT being utilized? Here is an example page for you to test on to see WHY this MUST be corrected. http://golowesstamps.com/egyptsales1.htm Please look into this and help ALL of us image backgrounded website owners out. Thank you JohnL
I agree with John Lowe. It is the responsability of the designer of the website to use wisely the transparent color. Or if you really want to, it should show a different warning and not the same as no background-color specified.
I think the John Lowe and Olivier Voutat are right, sometimes we need backgrounds transparents in your website, otherwise he will be strange No one will fix this? Remember: We are talking about WEB STANDARDS nothing ESTETIC (of course is essential too, between don't have priority over the standards) Sorry my english... []'s
For me the solution is a simple one, if not a happy one. I simply will not be using the CSS Validation Image/Link on my web pages.
I suggest that not "transparent" but "inherit" to warn about.
so which was the final solution to this?
(In reply to comment #7) > so which was the final solution to this? No final solution, the change was made by a malicious and/or clueless user batch changing a great number of bugs at the same time. We've reverted the bugs to their normal state.
We moved the "level" of this warning to the lowest level, amongst other warnings of potential accessibility issues. I think this is the closest we can get to consensus. Moving to [close] this bug.