Invalid code is the kind of thing that keeps me up at night, so I validate as often as I can. I have to make exceptions for CSS3, but its advantages are worth it.
Since i used OOCSS Grid ( http://wiki.github.com/stubbornella/oocss ) my css validation fail. More over with C.M.S (i use TYPO3) and mainly the client's integration, Html validation will fail too.
Lippe - 15 years ago
I always validate my code! Too bad, there are always validation errors when using WAI-ARIA etc, but I'm ok with those...
anders - 15 years ago
proper validation has taken a back seat to on the fly validation methods such as your trusty firebug and web dev toolbar, if i ever do validate, its for stupid things i may have missed like closing tags and incorrect header syntax as opposed to missing alt tags and stuff like that
HTML 5 is "mostly" supported on the W3C validation site: http://validator.w3.org/
If valid HTML 5 you will only see a warning stating, "Using experimental feature: HTML5 Conformance Checker."
CSS 2.1 validation should give you warnings about CSS 3 properties such as: "Property opacity doesn't exist in CSS level 2.1 but exists in [css3]"
When the W3C CSS validation service (http://jigsaw.w3.org/css-validator/) is set to validate CSS 3, it is only the browser "proprietary" properties such as: filter:, -moz, -webkit, etc. that cause validation errors.
And check out another cool validation tool from W3C (it's beta, still a little buggy): http://qa-dev.w3.org/unicorn/
I'll generally try and validate my XHTML, but if there are one or two things which enhance user experience but cause the page to fail validation, I'll let it slide (Google Maps, the occasional IFRAME).
Eric Peacock - 15 years ago
It's OK to have some validation errors - the validator isn't perfect. It's simply a guideline to catching things that can easily be missed. Or it's a learning tool if you're not fully able to pump out clean source by hand yet.
CSS3 properties are probably built with progressive enhancement in mind, so even if they pull up errors they won't affect the overall user experience when unsupported. Eventually the validator may fully support CSS3 as well.
I definitely make sure the XHTML/HTML 5 code is fully compliant and semantic. Now with the CSS, I'm in the same boat as Adam H. with the CSS 3 properties (especially the -moz and -webkit border radius properties).
I do my best to make sure every site I build is 100% valid, but sometimes there are cases where it's just not possible. I usually run into problems with CSS3 properties that the validator doesn't recognize, like specific calls for Firefox or Safari.
I was just talking about this yesterday as well lol,
I personally think its great web practice to ensure that the website passes validation, or if you have embedded javascript that it validates as much as possible.
not every site will validate 100% however i always try
I just wanted to mention that you can also validate using a small javascript as a bookmark. I wrote a simple howto here:
http://joe-riggs.com/blog/2009/12/firefox-create-a-bookmark-that-validates-html/
thanks-
Invalid code is the kind of thing that keeps me up at night, so I validate as often as I can. I have to make exceptions for CSS3, but its advantages are worth it.
Since i used OOCSS Grid ( http://wiki.github.com/stubbornella/oocss ) my css validation fail. More over with C.M.S (i use TYPO3) and mainly the client's integration, Html validation will fail too.
I always validate my code! Too bad, there are always validation errors when using WAI-ARIA etc, but I'm ok with those...
proper validation has taken a back seat to on the fly validation methods such as your trusty firebug and web dev toolbar, if i ever do validate, its for stupid things i may have missed like closing tags and incorrect header syntax as opposed to missing alt tags and stuff like that
@ev149,
HTML 5 is "mostly" supported on the W3C validation site: http://validator.w3.org/
If valid HTML 5 you will only see a warning stating, "Using experimental feature: HTML5 Conformance Checker."
CSS 2.1 validation should give you warnings about CSS 3 properties such as: "Property opacity doesn't exist in CSS level 2.1 but exists in [css3]"
When the W3C CSS validation service (http://jigsaw.w3.org/css-validator/) is set to validate CSS 3, it is only the browser "proprietary" properties such as: filter:, -moz, -webkit, etc. that cause validation errors.
And check out another cool validation tool from W3C (it's beta, still a little buggy): http://qa-dev.w3.org/unicorn/
Since HTML 5 doesn't validate and neither does CSS3, I only do it sometimes.
I'll generally try and validate my XHTML, but if there are one or two things which enhance user experience but cause the page to fail validation, I'll let it slide (Google Maps, the occasional IFRAME).
It's OK to have some validation errors - the validator isn't perfect. It's simply a guideline to catching things that can easily be missed. Or it's a learning tool if you're not fully able to pump out clean source by hand yet.
CSS3 properties are probably built with progressive enhancement in mind, so even if they pull up errors they won't affect the overall user experience when unsupported. Eventually the validator may fully support CSS3 as well.
It's just a matter of knowing what to ignore.
I definitely make sure the XHTML/HTML 5 code is fully compliant and semantic. Now with the CSS, I'm in the same boat as Adam H. with the CSS 3 properties (especially the -moz and -webkit border radius properties).
Doug S. makes a great point. It is becoming more common for the sites I code to fail strict CSS 2.1 validation due to the use of CSS 3 properties.
Most common culprits are -moz and -webkit border radius properties.
However, I always make sure to keep the XHTML/HTML 5 code fully compliant.
Was having this discussion with a lecturer the other day...
I try and make sure all my sites validate, but does it make a site "bad" if it doesn't?
I always validate my code to be a WC3 validated.
I do my best to make sure every site I build is 100% valid, but sometimes there are cases where it's just not possible. I usually run into problems with CSS3 properties that the validator doesn't recognize, like specific calls for Firefox or Safari.
Yes and no. My last few sites haven't validated but that's because I have been using CSS3 in all of them for progressive enhancement.
I make sure my XHTML validates as much as possible (dogmatically so) but I'll let my CSS slide a bit because of CSS3 rules.
I guess you could say I use web standards and validate everything that the W3C currently validates fully.
I was just talking about this yesterday as well lol,
I personally think its great web practice to ensure that the website passes validation, or if you have embedded javascript that it validates as much as possible.
not every site will validate 100% however i always try
Regards
Craig