"Who is correct isn’t important. What should be important is that browsers put consistency across themselves first." No way - The only way we'll end up with co

"Who is correct isn’t important. What should be important is that browsers put consistency across themselves first." No way - The only way we'll end up with compatibility across browsers is to have unambiguous (as much as possible) specifications that define how they should behave and for browser users to insist their browser vendor aligns with the standard. I lived through that past and have no desire to repeat it. If you think about it from a network theory perspective, each of the browsers is only trying to be compatible with one other party (the specification) in this mode. The alternative is that each browser is trying to be compatible with "n - 1" other parties where n is the number of browsers in the pool. And the total effort is the classic (n * (n - 1)) / 2 "connections", so the browser industry would be wasting a lot of effort. Worse yet, there's no single release point. Consider that browser A makes changes to be compatible with browser B (because that behavior seems correct compared to browser C). Unbeknownst to them, browser B is about to change their behavior to be compatible with browser C. Now the A-team's work is either wasted or yet another incompatibility. Browser-focused standards are the best thing that happened to the web in the last 10+ years. - http://caniuse.com/ http://caniuse.com/ - http://html5readiness.com/ http://html5readiness.com/ (now a bit dated)