Acid3 Test Released 309
An anonymous reader writes ""The Web Standards Project has announced the release of Acid3, the latest test designed to expose flaws in the implementation of mature Web standards in browsers. 'By making sure their software adheres to the test, the creators of these products can be more confident that their software will display and function with Web pages correctly both now and with Web pages of the future. The Acid3 Test is designed to test specifications for Web 2.0, and exposes potential flaws in implementations of the public ECMAScript 262 and W3C Document Object Model 2 standards.' Screenshots at the Drunken Fist site show the success of Safari 3 (which originally scored 31, but is now Scoring 87/100) IE6, and IE7 (massive fail, of course)'." There are additional discussions of the new test happening around the web.
Re:Firefox (Score:5, Interesting)
Re:Firefox 2.0.0.12 (Score:4, Interesting)
I'm not sure how many actually knows this. *shrug*
How do the acid-test creators test the acid test? (Score:5, Interesting)
Re:I've always wondered (Score:2, Interesting)
Just found it for Firefox 3.0 Beta (3) (Score:3, Interesting)
That said, I looked at a couple of the notes on Bugzilla for Firefox and they are already looking at the bug list... wonder who will be the fastest to fix the most....
W3C validator (Score:4, Interesting)
Perhaps, I am missing the point of these acid tests. I'm not a web developer by trade, so I don't claim to be an expert on CSS. From personal experience, CSS has allowed me to use much less complex HTML in the little web publishing I have done. I never seem to get consistent results when I test my pages in different browsers. I hope that these "standards" Acid tests lead to greater compatibility across browsers.
Do these tests increase compatibility by pushing the envelope on new standards, or are they just a browser-war pissing contest?
Re:Firefox (Score:3, Interesting)
Re:Firefox (Score:3, Interesting)
Besides, I see these as a process or goal -- giving the browser makers something concrete and visual to shoot for, as well as an easy way for users to judge the quality of their browser of choice.
Bullshit. The Acid tests have become the SAT's of the browser world. People *think* it's a measure of how standards compliant your browser is, but all it *really* is, is a measure of how well your browser does on the acid test.
That's it, nothing more, nothing less. The acid test is incredibly nit-picky and it's possible to even argue some of the decisions the guy has made about how things should be rendered (i.e. questioning his interpretation of the standard). And it's important that if your browser fails the acid test, but looks fine when you surf fark/slashdot/cnn/myspace, then whothefuck cares? The browser exists to deliver content to you; not to make some jackass feel happy that his CSS and Ajax code is the hardest thing to render in the known fucking universe.
I really, really wish people would get over the Acid tests; perhaps in favor of "the CNN test", or the "does it work with my proprietary intranet badly-coded webapps?" test. If it passes these, then just roll with it.
~Wx
Re:Firefox 2.0.0.12 (Score:3, Interesting)
Your numbers are quite different than mine. I scripted all the browsers/OS's I had handy from the sunspider javascript test last week and ran them on Acid3. The results are here [slashdot.org].
Where do you get a nightly of Opera? I ran the beta version they have up tonight and got 59/100 on OS X and it crashed on Linux and Windows XP. In any case, the best number I got was Safari 3.0.4 with a week old nightly of Webkit on OS X, which got 86/100. The Firefox 3 beta also did well getting 67/100 on OS X and Linux (but only 59 on Windows for some reason). Other people have gotten slightly better numbers for both using a more recent nightly of Firefox or Webkit.