Browser Standards Support Comparision
Ok this may be a loaded question. I am looking for a resource that can tell me what browsers support what standards and to what rate. What I am looking to compile is a table that I can use to lookup and determine that say Netscape 4.5 supported the W3C CSS Standard 100% and the CSS 2 Standard 80% but CSS 3 0%. This is to present to various interested parties some measurable information so that we can decide what standards we wish to support and allow on our web corporate web sites. Any resources to help with this would be greatly appreciated.
Re: Browser Standards Support Comparision
Believe it or not, this can get tricky. One thing to look at:
This site will tell you what supported what, but not the standard itself. For that, however, you could cross reference the standard from the W3C which can be, more or less, a pain. This is just for HTML. You can also look here for their CSS material:
I am not really advocating this site overly much - just pointing it out. For another site that does good CSS information, along with a lot of other stuff, check out:
You also, however, have to pay attention to standards support on different operating systems. IE 5 on PCs and IE 5 on Macintosh had much different standards support. Netscape, prior to 6.x, was notoriously bad in their support of most of the standards for W3C (such as HTML, XHTML, and CSS) and did not even really support XML until 6.x. The 6.0 version was better but had a lot of flaws and the 6.1 version actually did quite well in terms of standards support.
You can find some information on the W3C site itself, most under some of their Talks. They discuss some of the current browser implementations at various stages and how much standards support exists within them. (For example, Opera has always been a pretty strict standards supporter.) There are also a few other sites than what I mentioned above but I tend to find them either sometimes inaccurate or just plainly out of date.
What I have found most helpful is writing your own test suites based on the standards. In other words, have a set of standard pages that you run against each browser. Make sure your pages follow the W3C standards to the tee (which you can get from the site) and then note the implementation problems in each browser. This is more time-consuming, of course, but it gives you readily available tests that you can always update and add to when things like XHTML make their way on the scene or MathML or anything else. I have found that to be the best way because often the Web sites and book references do not keep up with the standards.
If you are curious as to how the W3C denotes the various standards, just check out: