Working together for standards The Web Standards Project

For a while now we’ve had a problem with the Acid 2 Test on the WaSP site. If you’re unfamiliar with the Acid 2 Test, it is essentially a test for browser vendors to use as a means to gauge their standards compliance. If your browser renders the Acid 2 Test page the same as the Acid 2 reference rendering, then you know you’re hitting the mark.

I’ll be honest: over the last 10 days, I’ve learned more about the Acid 2 Test than I ever wanted to know. If you want to do the same, you might start with Acid 2: The Guided Tour.

The short version is that part of Acid 2 is a test for the way a browser handles an <object> element when the data attribute references a URL that returns an HTTP status code of 404. A number of caching rules, mod_rewrite rules and redirects all collided to create a problem with our 404. The cached version of our 404 page was returning an HTTP status of 200. As you might expect, this basically makes the test useless.

Acid 2 was broken. Now it is not. Carry on.

Your Replies

#1 On July 25th, 2008 11:23 am Eric Roger replied:

problems -> www . webstandards.org /files /acid2/test. html#top

Post a Reply

Comments are closed.