Comments on: Webkit now up to 92/100 on Acid3

By: hmm

hmm — Tue, 18 Mar 2008 16:30:25 +0000

Opera: new development snapshot has 77/100
____________
Windows 9841
Mac 4716
UNIX 1875

By: Stifu

Stifu — Tue, 18 Mar 2008 07:32:32 +0000

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.

By: David Baron

David Baron — Mon, 17 Mar 2008 23:08:09 +0000

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.

By: Lars Gunther

Lars Gunther — Mon, 17 Mar 2008 20:00:52 +0000

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

By: Emil Ivanov

Emil Ivanov — Mon, 17 Mar 2008 17:44:36 +0000

Great the code gone :)
Add two paragraphs, in the first put input type text.
In the second add input type submit.

By: Emil Ivanov

Emil Ivanov — Mon, 17 Mar 2008 17:41:35 +0000

This is very brief testcase since here is not very good place to write testcases.

input {width:100px;}
input[type="submit"] {width:auto;background:grey;}

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.

By: Robin

Robin — Mon, 17 Mar 2008 15:36:15 +0000

Emil: I’ve not really noticed any problems with Safari + width:auto? Got a testcase or link to a bug so I know what to watch out for? Thanks!

By: Neal G

Neal G — Mon, 17 Mar 2008 14:48:23 +0000

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.

By: Emil Ivanov

Emil Ivanov — Mon, 17 Mar 2008 14:21:48 +0000

Too bad the webkit team is only aimed at the points in tests. And not fixing some basic stuff, which is very funny. How the browser with the most points in acid3 cant handle rules like width:auto.

By: James Hopkins

James Hopkins — Mon, 17 Mar 2008 10:12:25 +0000

@Dot. – Thanks for the sharing that useful resource
@Stifu – They must have written the announcement literally minutes after I posted this article. Thanks for pointing it out; I’ll update the article a bit later on