"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."

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