The supposed be-all/end-all for testing a browser’s worth is whether it scores a 100 on the Acid3 test.
I don’t pay attention to these tests because compatibility doesn’t really count for much; this is especially true since the vast majority of web sites fail (and fail hard) the W3C Validation Service (Google.com even fails that test badly). If web designers don’t care if they pass W3C, why should we care about Acid3?
For you Firefox users out there, you’ll notice the brand new Fx 4 does not score a 100. Does this mean the browser is “bad”? Of course not, and this is why. The “failure” has to do with features almost nobody save for web designers actually care about – and you’re probably not a web designer.
Why are web standards so largely ignored?
The reason standards are either given an “Eh, whatever” response is because browsers by nature are programmed to be very forgiving when it comes to rendering web pages. For example, if you were designing a table with the old-school <table> tag in your web page, if you forgot to close out the markup with </table>, guess what? The table still displays as it should even though the code is completely improper – and that’s just one of hundreds of examples where the browser does its job even if the code is flat-out wrong.
If you ever run into anyone that says a browser is “bad” because it doesn’t pass some specific test that nobody cares about, ignore them. Use whatever browser you want, because for day-to-day browsing, nobody cares if a browser passes with perfect scores or not.
The PCMech.com weekly newsletter has been running strong for over 8 years. Sign up to get tech news, updates and exclusive content - right in your inbox. Also get (several) free gifts.