I still don't understand the obsession with Acid tests - they measure performance in incredibly obscure areas and have a comparatively small bearing on real world performance. Webkit and Opera in particular have designed to the test to an extent, resulting in good scores but not necessarily comparable general compliance.
I'm also slightly confused by the use of the word "still" - none of these bugs are severe enough to risk breakage leading up to a release candidate. I believe far more relevant are performance, bug fixes, features and HTML5/CSS3 support (which make far more of a contribution to moving the web on that Acid Test scores do) - areas in which Firefox 3.5 has improved dramatically. Talk about focusing on the negatives...
Slashdot Mirror
I still don't understand the obsession with Acid tests - they measure performance in incredibly obscure areas and have a comparatively small bearing on real world performance. Webkit and Opera in particular have designed to the test to an extent, resulting in good scores but not necessarily comparable general compliance. I'm also slightly confused by the use of the word "still" - none of these bugs are severe enough to risk breakage leading up to a release candidate. I believe far more relevant are performance, bug fixes, features and HTML5/CSS3 support (which make far more of a contribution to moving the web on that Acid Test scores do) - areas in which Firefox 3.5 has improved dramatically. Talk about focusing on the negatives...