Kudos to the Webkit guys for obtaining such a high score after Acid3’s launch only earlier this month; I recommend you subscribe to the blog to keep up with their work, as it’s pretty active at the moment and I’m sure that activity is only going to increase the closer they come to passing Acid3.
A meta bug has been created in their Bugzilla which you can use to keep track of their progress and outstanding bugs relating to an Acid3 pass.
Other browser scores below:-
- IE8 – 17/100
- Opera nightly (build 4681) – 65/100
- FF3b pre 5 – 70/100
You can skip to the end and leave a response.
You say there’s no point mentioning it, but if it indeed so low many people (myself included) may be curious as to exactly how low it is. We’re nerds, so exact numbers are always a good thing.
@Covarr – sorry I was being a bit sarcastic; I blame the frustration of the IE8 score for my comment! It scores 17/100
@hmm – I don’t currently have access to the latest build, but thanks for the update. I’ll update the post a bit later with the result
Emil, you bring up a good point about browser vendors only fixing things that are in these tests. Look at the IE team, with IE8 they ended up fixing their browser for Acid2 (although they suspiciously claim it wasn’t on purpose.) Unfortunately there are still a lot of common day bugs that get ignored because they do not make it in these tests.
This is very brief testcase since here is not very good place to write testcases.
Create a page with basic structure and add this and you will see how the button is going in the right side, then remove the with:auto to see the result. Also you can remove the styling at all from the button and it will be ok, but in some pages default behavior of elements is not good.
@neal. MS has contributed a truckload of CSS 2.1 tests to W3C. They have a long way to go still but what you said simply is not true.
Passing W3C test suites is of course much more important than other tests, but they serve a purpose too: Making people aware of interoperability issues.
Mozilla also has a meta-bug at https://bugzilla.mozilla.org/show_bug.cgi?id=acid3 tracking the issues that need to be fixed. If you want to help making sure the necessary Mozilla bugs are filed and tracked, that would improve the chances of Mozilla passing Acid3 sooner.
That said, just because something is in Acid3 doesn’t mean it’s our highest priority to fix. We try to focus on doing the work that we think will be most effective at moving the Web forward. Sometimes this will agree with Ian’s priority list; sometimes it won’t.
Webkit now at 93/100: http://webkit.org/blog/161/webkit-hits-93100-in-acid3/
But because the Acid3 test was changed. Due to this, Firefox (trunk) also got an extra point and is now at 71/100.