Slashdot Mirror
First Look At the ACID3 Browser Test
ddanier writes "Now that all major browsers have mastered the ACID2 test (at least in some preview versions), work on ACID3 has begun. The new test will focus on ECMAScript, DOM Level 3, Media Queries, and data: URLs. 100 tests will be put into functions each returning either true or false depending on the result of the test. The current preview of ACID3 is still missing 16 tests."
Just tested, Opera 9.5Beta and Firefox 3 Beta3pre are pretty impressive.
There is a spark in every single flame bait point.
Firefox 2.0.0.10 fails the test
Camino 1.0.3 crashes when starting the test
Safari 2.0.4 doesn't even get started. It says I need to enable JavaScript, which is enabled.
"In case of emergency, break glass. Scream. Bleed to death."
Final scores of course are subject to change on the final test:
* - script takes long enough to run that browser prompts you to kill it.
ACID2 and ACID3 tests don't test if browsers are standard compatible. They only test some features. To get better overview of the standards supports, try this page:
http://www.webdevout.net/browser-support-summary?IE7=on&FX2=on&OP9=on&uas=CUSTOM
Opera 9.5Beta and Firefox Beta3pre failed too. Just FYI.
There is a spark in every single flame bait point.
No, it isn't.
Which is why the GP shouldn't be modded as "Insightful."
The ACID Tests are meant to test certain parts of the proposed standards.
Passing the Test doesn't imply standards compliance.
BUT
Standards compliances DOES imply passing the tests.
... and looks somewhat like the reference image...
Opera 9.2.4 (Windows) reaches 55 (but looks horrible)...
Firefox 3 looks like the best shot at it so far.
I'm old enough to remember when discussions on Slashdot were well informed.
Everything in the ACID3 test is at an implementable stage (look at Anne's blog post in the summary (i.e., RTFA)), and has been since 2004.
Yeah, it was David Hyatt who was working on getting Saf to pass (and got it to be the first browser to pass in any build, and the first to have a generally available release (i.e., a non-development build, even if public) -- the latter being the only thing that truly counts for passing the test).
http://weblogs.mozillazine.org/hyatt/archives/2005_04.html#008011 details the bug (in this case, it was the test itself that was wrong -- not the reference). The reference rendering for Acid3 is likely correct as the actual rendering isn't overly complex (the complexity is in the ECMAScript and DOM support), though with the complexity of some tests there could easily be bugs in the test again.
Firefox is a major browser, however the version which passes ACID2 is Firefox 3, I think the first build which passed was around this time last year so either go with the development release (FF3 is currently in Beta).
--- Users are like bacteria -> Each one causing a thousand tiny crises until the host finally gives up and dies.
Excellent. These two, especially, need to be tightened up (and in some cases, fixed) across the browsers.
Safari 3 is available for both Tiger and Leopard. The 10.4.11 update includes Safari 3.
After prompting me if I wanted to open empty.txt, it segfaulted my Konqueror with this backtrace:
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".[Thread debugging using libthread_db enabled]
[New Thread -1232832304 (LWP 8079)]
[KCrash handler]
#6 0xb609a9a1 in ?? () from
#7 0xb5f325d4 in ?? () from
#8 0x081e1f38 in ?? ()
#9 0xbfcde5a4 in ?? ()
#10 0xbfcde588 in ?? ()
#11 0xb60fe4fd in DOM::NodeFilter::acceptNode () from
Backtrace stopped: frame did not save the PC
I think we have a zeroday on our hands boys!
fyi
konqueror from kde3 crashes
konqueror from kde4 does a pretty good job (compared to ie7 and ff2)