- This topic is empty.
Viewing 4 posts - 1 through 4 (of 4 total)
Viewing 4 posts - 1 through 4 (of 4 total)
- The forum ‘CSS’ is closed to new topics and replies.
The forums ran from 2008-2020 and are now closed and viewable here as an archive.
if you guys take a look at my wordpress website,
http://www.nintensity.net/revscene
you can see that W3C Validator is detecting CSS3-valid codes as errors. Things such as
"Property -moz-opacity doesn’t exist : 0"
"Property -khtml-opacity doesn’t exist : 0"
"Property -x-system-font doesn’t exist : none"
And other valid CSS3 codes are outputting it as a bunch of errors. Can anybody help? I’m still trying to figure this out.
Regards,
Nintensity
Don’t worry about them. I don’t believe CSS3 is considered valid yet in the WC3 validator, so it will show an error even if they are perfectly valid.
Ahh thanks falken!
I’m also getting an opacity error.
"Parse Error opacity=70)"
whenever I use an IE Opacity hack, for example, " filter:alpha(opacity=100); "
It comes up as an error during my validation. You can even check it for yourselves.
Is this a known problem that is unfixable?
Any css hack will error thru w3c…
Validation is great or catching errors like typos or syntax errors… but if you are using -moz targeting or any other "tricks" you will see an error
doesnt mean its wrong or bad or "invalid" its just not the standard…