Acid2 fun

People around my world are having much fun in watching Acid2 race. Who’ll be first? Who’ll release first?
Well. Imho whole tests isn’t more important than near 300 others bugs in b.m.o about CSS, and it’s absolutely not important who will release it first. Talking about such small differences like two weeks or a month makes it absolutely not important – If all major web engines will pass Acid2 by this year what’s the difference who made it first? It’s not innovative nor patented (yet) so I think we should calm down 🙂

Safari team should be praised, with iCab being the second and Konqueror third. Presto and Gecko are a few bugs from being ready, so riots can be finished, people can go home and enjoy real life things like recent news that our european politics are autistes hardly understanding signals from nations.

3 replies on “Acid2 fun”

If anything, the competition between browsers to support Acid2 is what’s going to cause all major web engines to pass Acid2 by this year. The race is not the ends, but it *is* the means to the ends, and therefore is a critical part of getting standards compliant browsers. Without the race, what incentive is there for browsers to pass the test? The only incentive I can think of is not looking bad compared to Safari and Konqueror. The race is on!

We shouldn’t calm down, but on the contrary get more excited about this race that’s heating up. Finally we’ll be able to actually use these standards that have been promised for years, but never delivered upon!

I would take the acid2 test more serious if the behaviour demanded by the test could be easily readout from the published spec. At least for row14 this is not the case, as only future versions of CSS2.1 will describe the necessary behaviour ( I’am less excited as Steve as I believe the test will only ensure that a couple of browsers coincide in edge case renderings.

“Well. Imho whole tests isn’t more important than near 300 others bugs in b.m.o about CSS”

As I understand it, one of Acid2’s design goals was to test those things which are important for backwards compatibility with new content on the web (e.g. nested object renderings). As Mike Shaver outlined in his XTech keynote, there is a move towards incremental improvements of what we have today, rather than the big-bang reinventions of HTML, CSS, PDF and OpenGL all at once (naming no names).

So, for today’s browsers to render tomorrow’s pages acceptably, even if they don’t support the latest technologies in 2008 or 2010, the fallback mechanisms need to be got working as a matter of priority. This is what makes some of these bugs more important than your average CSS bug.

Of course, Hixie did throw a few other things, like obscure comment parsing 😉

Comments are closed.