Failed to Passed W3C Validator
Today I rechecked this blog at W3C Validator.
Unfortunately I did not passed the validator!
It said to me, well it’s a text actually and sound like this.
This page is not Valid XHTML 1.0 Strict!
Failed validation, 12 Errors
So this post is actually for testing purpose. But you can read it too as this is not as useless as what it suppose to be.
Why we should validate?
- Cross browser compatible.
- Compatible for future browser.
Why validate is hard?
- Even _target blank attribute is not allowed.
For my case which I use strict doctype.
It still valid if you use transitional doctype. So don’t worry too much. - All styling is depends on stylesheet.
If you lack of css knowledge like me, you’ll have a hard time like me too.
Validate is a must and a challage for all web designer. A valid page also crawled and spidered easier than unvalid page. – Source; unverified
This is a valid video flash embed.
This is a valid iframe code for strict doctype!
By PANGERAN.ORG.
A valid xhtml always use lower character for the code snippset.
Then I check this post’s code via direct input.
Yesss!
I’ve passes with the validator with no errors nor warnings.(For now…)
As the time goes by, you might easily make mistake and lazy. So do I. He he.
This Page Is Valid XHTML 1.0 Strict!
Passed validation
See next page for the valid youtube video code or a valid iframe code.

about 1 year ago
Not wrong if you visit daniiswara.net for all about html syntacs or contact to his ym. (iswara_wp@yahoo.com)
about 1 year ago
Actually I know how to validate…
It is about “the laziness”…
about 1 year ago
You can check it out at:
http://validifier.com/
Hope that helps!
about 1 year ago
Anyway, is that code open source?
It might be a great helps if it integrated into a wordpress plugins… :mrgreen:
about 1 year ago
about 1 year ago
It’s not open source at this time, but we’re reviewing open source options. We definitely want to contribute back to the community in any way that we can.
I’m glad you like it!
about 1 year ago