Dave
|
Anyone else getting tons of errors when checking your site on the WC3 service.
I created a 4 page html site with only typing in text and have 199 errors! Yikes
It is using V4 RC2 so maybe it's not perfected yet?
|
| |
Dave B
|
Anyone?
|
| |
Harold
|
Mega tons of errors!!
|
| |
Kris
|
Link to the page? Can't really offer an opinion without seeing the type of errors you get.
|
| |
Dave B
|
Doesn't matter what site, any version 4 built site has tons of them.
http://jigsaw.w3.org/css-validator/validator?profile=css21&warning=0&uri=http%3A%2F%2Fenglishsolutionswi.com%2F
|
| |
Kris
|
Isn't your problem that you're trying to validate css3 against a css2.1 validation rules...
|
| |
Daviator
|
YES! My site returns 160 errors when checked against CSS3
|
| |
Kris
|
The CSS3 standard and best practises are not fully developed yet so why do you expect your css3 code to validate? I know there's a option to att parameters to the wc3 validator so that it actually attempts to validate CSS3 but even that won't give you complete cover of the current ruleset.
|
| |
Kris
|
*to add parameters to the WC3 validator...
|
| |
Dave B
|
Quote Kris:
The CSS3 standard and best practices are not fully developed yet so why do you expect your css3 code to validate? I know there's a option to att parameters to the wc3 validator so that it actually attempts to validate CSS3 but even that won't give you complete cover of the current ruleset.
Thanks Kris, I guess that makes sense. The html validated OK as html5 so I assumed the css should too.
Quote :This document was successfully checked as HTML5!
|
| |
Kris
|
You could try this:
http://jigsaw.w3.org/css-validator/validator?uri=http://your_site.com&profile=css3
|
| |
Dave B
|
Still 136 errors. I asked support what they thought and haven't heard back yet.
|
| |
calsnoboarder
|
Dave B, make sure you update this thread when you do hear back...
|
| |
Dave B
|
Quote :1. Please validate on CSS level 3 2. most of the error related to the properties with vendor prefixes (-moz-, -webkit-, -o-). The vendor prefix is a proprietary function that is not w3c valid. Since Artisteer 4 supports CSS 3 these prefixes are required for some old browser versions.
Seems like Kris was correct, the whole thing is still a work in progress. The html 5 is validating which is most important.
|
| |
Dave B
|
Any advanced gurus here that can give some insight to the results would be appreciated.
|
| |