My point is that we need to get beyond accepting incorrect code. Haven't we yet learned that Standard's Compliance is the best way to interoperability? What's the point in continuing to bend over backwards for quirks mode?
What's the point of rendering incorrect code correctly? The Acid tests are stupid and useless. I'd rather see steps toward more standards compliance...so people can see when they've made a mistake coding.
I agree, and disagree. The number one thing in my mind is that web browsers need to implement fully every W3C standard in use, such as SVG, XHTML, CSS2.1, and all the web browsers need to implement future support as well, for CSS3 and HTML5.
As for the Acid tests, what's the point?
Slashdot Mirror
Browsers are more consistent than ever in what they support, and that's somehow a bad thing? Clearly the writer of that article isn't a web developer.
I have thought about it, and Evolution doesn't make a lot of sense. Blind faith is evolution, don't let anyone fool you.
My point is that we need to get beyond accepting incorrect code. Haven't we yet learned that Standard's Compliance is the best way to interoperability? What's the point in continuing to bend over backwards for quirks mode?
What's the point of rendering incorrect code correctly? The Acid tests are stupid and useless. I'd rather see steps toward more standards compliance...so people can see when they've made a mistake coding.
I agree, and disagree. The number one thing in my mind is that web browsers need to implement fully every W3C standard in use, such as SVG, XHTML, CSS2.1, and all the web browsers need to implement future support as well, for CSS3 and HTML5. As for the Acid tests, what's the point?