Linked by Thom Holwerda on Wed 26th Mar 2008 21:26 UTC, submitted by ohxten
Opera Software "Since the test was officially announced recently, our core developers have been hard at work fixing bugs and adding the missing standards support. Today we reached a 100% pass rate for the first time! There are some remaining issues yet to be fixed, but we hope to have those sorted out shortly."
Thread beginning with comment 306904
To read all comments associated with this story, please click here.
Firefox dev: "Acid3 is basically worthless"
by MollyC on Thu 27th Mar 2008 17:36 UTC
Member since:

During my daily visit to, I found this item that struck me as pretty amusing. ;)
Acid3 is basically worthless
I was looking over the spreadsheet covering Mozilla's Acid3 failures, and it struck me that very few of the fixes would substantially improve the Web or the browser. They are bugs and they will be fixed (except maybe SMIL... wtf?), but they don't impact authors or users at all. Looks mostly like an opportunity for grandstanding about "commitment to standards." I think testing createNodeIterator while text nodes don't interoperate is both misguided and hypocritical.

Besides, commitment to standards is strong at Mozilla, where we don't constantly seek to rubber stamp our own implementation.

There's another thread saying that since Firefox 3 is in its final stages of development, they will be fixing no Acid3 bugs for Firefox 3, which is a sensible policy.

Edited 2008-03-27 17:43 UTC

Reply Score: 3

crislevin Member since:

Im not gonna call it useless, but if webkit can just selectively implement small portion of standard just for the test. There is something not right with it.

Its nice to reach 100/100, but by doing so in such a "pass just for the sake of passing" manner, is not meaningful.

Edited 2008-03-27 19:33 UTC

Reply Parent Score: 1

umccullough Member since:

This is also my understanding of the Acid tests (yes, both 2 and 3 exercise unrealistic corner cases).

Thus, I'd rather a browser focused initially on supporting the most important standards properly *first* and then go back and fix the corner cases.

The approach mentioned - to freeze the FF3 code and work on Acid3 compliance later is absolutely reasonable. Why distract the developers with "fantasy-land" compliance issues while they have more important things to focus on now and here.

That said, I hope Mozilla/Gecko devs do at least work on some of the issues once the FF3 release is finished ;)

Reply Parent Score: 2