Sorry, but you are wrong.

1. Webkit has passed all 100 subtests for a great while. They have also passed the rendering part of the test since spring. What is new is the announcement that they also pass the smoothness criterion. That is what is “now” – the rest is old news.

2. Mozilla is not far behind. Their internal builds score 97. They get the rendering part almost perfectly (one really small glitch left).

In general they are doing a more thorough job on each bug they fix. There is actually one issue unsolved with the test as such!

[tekkie.flashbit.net]

In this game, Mozilla is quite far behind.

Is also insightful

For those who have 3.0b5 try this

about:robots

That was actually really funny. I especially like what happens when you click the “try again” button.

about:robots

netster007x wrote:

Now here they are in order of site compatibility (least to greatest)…Opera, Safari, Firefox, Internet Explorer
That’s a strong negative correlation (-1) between standards compliance and site compatibility!

Yeah, but that’s just because IE has the biggest marketshare and Firefox has tried to make its engine more compatible with how IE displays thing in order to gain marketshare as well. You cannot compare it like that (unfortunately)

That is exactly right. There is really no correlation (positive or negative) to standards compliance and ability to render a site correctly. Opera takes a lot of steps to ensure that major sites render correctly (such as Gmail), and it’s merely because developers don’t want to take the time to test and debug any problems. With IE8 becoming more standards compliant we might see a more uniform Internet in the future.

Now here they are in order of site compatibility (least to greatest)…Opera, Safari, Firefox, Internet Explorer

That’s a strong negative correlation (-1) between standards compliance and site compatibility!

Yeah, but that’s just because IE has the biggest marketshare and Firefox has tried to make its engine more compatible with how IE displays thing in order to gain marketshare as well. You cannot compare it like that (unfortunately)

I do see the point of Acid2 because the browsers that support that generally support standards better (= easier to develop cross-browser compatible websites), but I’m not sure if this is the case with Acid3 yet. If Mike Shaver is right, the impact of Acid3 on the web experience will be minimal, which was not the case with Acid2.