In old-style HTML, you never really knew how your pages would look on various browsers. In fact, you never really knew if your page was even written properly. Some mistakes would look fine on one browser but cause another browser to blow up…
The idea of #validation is to take away some of the uncertainty of HTML.
It’s like a spell checker for your code.
My regular spell checker makes me feel a little stupid sometimes because I make mistakes.
I like it, though, because I’m the only one who sees the errors. I can fix the spelling errors before I pass the document on to you, so I look smart… Yeah! 😁
What is Validator?
A validator is actually the front end of a piece of software that checks pages for validity.
It looks at your web page’s doctype and sees whether the page conforms to the rules of that doctype. If not, it tells you what might have gone wrong and tell you to rectify your errors.
Most important Validator is W3C validator at http://validator.w3.org.
You can submit code to a validator in three ways:
✦ Validate by URL = This option is used when a page is hosted on a web server. Files stored on local computers can’t be checked with this technique.
✦ Validate by file upload = This technique works fine with files you haven’t posted to a web server. It works great for pages you write on your computer but that you haven’t made visible to the world. This is the most common type of validation for beginners.
✦ Validate by direct input = The validator page has a text box you can simply paste your code into. It works, but I usually prefer to use the other methods because they’re easier.
Hope you like this session!
Show some love and share with your friends 💞