Twitter
Flickr
RSSThe “Valid HTML/CSS” Bug
Feb 4
Article, Discussion CSS, HTML, valid, web standards No Comments
When you’re proclaiming valid HTML & CSS on your web site, just make sure it actually is valid and not just some trendy attempt to look the part. e.g. this web site. Close your meta tags, clean up the little oversights and you got yourself a gem dandy of a site, then you will be in fact, 100% valid.
It compares to sticking a gas mileage number on a car, say 30 MPG and in fact only getting 25 MPG. Close, but not close enough.
Also, to the owner of the above link, should you be reading this, please switch your charset to utf-8 instead of iso-8859-1. The presentation of some characters in copies of this document may be defective. e.g. due to lack of font support. There may be an argument as to which is best, but;
In theory, any character encoding that has been registered with IANA can be used, but there is no browser that understands all of them. The more widely a character encoding is used, the better the chance that a browser will understand it. A Unicode encoding such as UTF-8 is a good choice for a number of reasons.
http://www.w3.org/International/tutorials/tutorial-char-enc/#Slide0110
You can read about them at the above link. The moral of this story? Don’t throw that little graphic, or any little graphic on your site that says it’s valid, when in fact, it isn’t. Make sure it throws back no errors first. Then, you can hang that passé .gif or .png on your site and be proud that indeed, your code has no errors.
Recent Comments