you don't know what you are talking about - not a single one of the browsers out there are compliant with with all the standards, and even the ones that "thnk" that they are compliant with is just a matter of opinion thats the trouble with just having browser standards and letting various companies determine for themselves what the standards actually mean and how to implement the browser functionality to "meet" those standards - in short the whole thing boils down to how the developers "interpret" the standards. in other cases they just outright choose not to support certain parts of the standards and that will be the problem with html5 - it sounds great, but we will have the same issues with html5 that we have now with certain browsers working one way and others doing something else when they are all reading the same code there is only one answer to this problem - have the same authority that writes the standards also test each browser and if it doesn't pass 100%, then it can not be released to the public till it is nothing more frustrating than to have to write 4 different variations of a html site just so it will render that same on all browsers - actually is not possible depending on what code you write as not all browsers have support for certain things in the css this is what makes Silverlight so great as a plugin - any code will work and render the same on any browser