Comments on: Acid3 Range Exception Test Fixed – WebKit hits 92/100

By: solipsism

solipsism — Mon, 17 Mar 2008 05:12:01 +0000

I hadn’t realized that was a new feature to assist developers. Thanks for the insight.

By: Maciej Stachowiak

Maciej Stachowiak — Mon, 17 Mar 2008 05:08:03 +0000

@solipsism The times displayed are just advisory to help browsers pass the “smooth animation” criterion. They were just recently added to the test, and are not failures. Also, you should be looking for the smooth animation with a cached load (load it once, close the window, load it again). In my experience, at least on a fast machine, the animation looks smooth for almost the whole test, it only visibly jitters on test 26, at least on a release build. We’ll have to speed up that test to claim a full pass as well.

By: Kody Bryson

Kody Bryson — Mon, 17 Mar 2008 04:54:17 +0000

Oh also, wouldn’t it be cool if you guys got an acid 3 browser fully released before IE and Firefox released an acid 2 compliant browser? No pressure.

By: Kody Bryson

Kody Bryson — Mon, 17 Mar 2008 04:51:15 +0000

I agree with your logic. I have felt that comments made by Microsoft that these tests weren’t important were made largely because their browser didn’t pass them. However, whether these tests test the “most important” parts is irrelevant. The point is that the tests find bugs. To say they’re not important is to say bugs are not important. And while they might not be the “most important” bugs, they’re at least the “most public” or the “most talked about”.

The tests absolutely should target the most obscure parts of the standard that require the most stages to be fixed to actually work. Like testing the finger hopefully makes sure there’s a wrist, elbow, and shoulder that all work to some extent. Behind every failed test are many bugs that need to be fixed. And each bug that needs to be fixed means some developer is reading a part of the standard and truly understanding it, probably for the first time. At that point a whole bunch of bugs will likely get fixed, not just the ones for the test.

By: solipsism

solipsism — Mon, 17 Mar 2008 04:51:14 +0000

It is amazing the speed at which this test is being passed, though I have noticed that the last few builds have introduced significant speed issues. While there are only 8 tests that aren’t being passed, there are many more that are taking too much time or too many attempts to complete. My average speed has gone from <1 sec to ~3 sec. After 10 tries test 00, 26, 32, 33, 37, 41, 46, 65, 69, 74 were all reported as passing but with completion issues, though not all on the same Acid3 rendering.

(I assume this is a known issue and I don’t know how to search to see if these have even been listed yet so I have not reported them to the bug list.)

— MacBook / 10.5.2 / 2.Ghz / 667MHz FSB / 4MB L2 / 3MB RAM / / Safari 3.1 / WebKit r31090 —

By: fastveg

fastveg — Mon, 17 Mar 2008 04:27:45 +0000

Amazing work guys – keep it up!