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."
u-bend
Can't we acid test the ACID Test server?
:-)
If it can't hold up, maybe it needs some work...
Finally, the bigger browsers are ACID2 compatible now. But suddenly those fuckers release a new ACID test. Now everybody's standard incompatible again. Let's see who succesfully implements ACID3 first.
Knowledge is power. Knowledge shared is power lost.
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.
Safari 3.0.4 (Windows) hangs at 60, Internet Explorer 7.0.5730.11 messes up so badly the result can't be read...
The test looks interesting, for sure. And it's going to raise the game for standards compliance!
I'm old enough to remember when discussions on Slashdot were well informed.
... 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.
Something I always wanted to know (applies to the older Acid tests, too): how do they render the reference image? Is someone creating them by hand? How do we know no mistake was made when creating the reference image?
Well, for IE6 it reports 100% of the standards as I can prove here! In your face Firefox!
http://stoploudness.org/
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.
Acid2 tests a particular interpretation of how the standards should be implemented.
"We receive as friendly that which agrees with, we resist with dislike that which opposes us" - Faraday
That would be pointless. If browsers are getting mere hacks to display the specific acid test page correctly, the jig will be up when web developers start using the features tested by that acid test and discover that the features don't really work. I suspect that no browsers have been tweaked to pass certain tests, as that tweaking wouldn't fool web developers for any significant period of time.
What a fool believes, he sees, no wise man has the power to reason away.
When Firefox makes news on this there are daily builds to test, source code to inspect and compile. One can see the progress first-hand.
There is no build of Microsoft Internet Explorer 8 to test. You are accepting something unverifiable as reality and thus talking about these browsers as if they're all on the same level. This suggests a new low: believing the illegal monopolist who tells you that their vaporware behaves in accordance with published publicly-implementable standards.
Digital Citizen