Haavard

Acid2 fails the Acid2 test

Thursday, 20. December 2007, 18:30:19

If you take the Acid2 test in any browser, you will notice that they all fail. This is not because all browsers suddenly stopped passing Acid2, but because of an error with the test itself.

Ian Hickson's comment in Mozilla's Bugzilla bug tracking system seems to indicate that it will be fixed after the new year, but in the meantime you can try a copy of the working Acid2 test over on Ian's site. The reason for the broken Acid2 test is also covered in the Bugzilla discussion:

It looks like an object element that's pointing to a non-existent page (http://www.webstandards.org/404/) should be falling through, but that page is now returning a response status of 200 (success) instead of 404.

Update 2007-12-22: It looks like this problem has been addressed, so the Acid2 test should be back to normal.

Internet Explorer 8 passes Acid2Microsoft files antitrust complaints against Google

Comments

WildEnte # 20. December 2007, 19:02

so does IE8 pass Acid2 or the borked acid2? (c;=

AyushJ # 20. December 2007, 19:08

@WildEnte- http://blogs.msdn.com/ie/archive/2007/12/19/internet-explorer-8-and-acid2-a-milestone.aspx#6816928

Originally posted by Arron -MSFT-:

.. Ian maintains a secondary copy on his site. http://www.hixie.ch/tests/evil/acid/002/

This copy seems to be working as expected in all browsers including IE8.

Jadd # 21. December 2007, 15:42

So why don't they say so on their front page?

Anonymous # 22. December 2007, 07:19

Anonymous writes:

Interestingly Opera 9.5 beta which has been released months ago "passes" borked Acid test...

How can it be? I mean, if it is borked, there has to be some form of borkness or Opera also doing tricks like nVidia usually do on benchmark tests?

scipio # 22. December 2007, 10:12

Originally posted by anonymous:

How can it be? I mean, if it is borked, there has to be some form of borkness or Opera also doing tricks like nVidia usually do on benchmark tests?

Well, according to Haavard's post (my emphasis):

It looks like an object element that's pointing to a non-existent page (http://www.webstandards.org/404/) should be falling through, but that page is now returning a response status of 200 (success) instead of 404.

In other words, something got broken recently.