Linked by Thom Holwerda on Wed 26th Mar 2008 21:26 UTC, submitted by ohxten
Thread beginning with comment 306795
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
what is the point of the test, then?
ACID2 tested how to interpret even faulty code (how certain errors should be handled) - I assume ACID3 is the same.
Sure - one test can't possibly cover every quirk; and definitely doesn't dictate the behaviour of possibly related things, but if a 100% on the test does not guarantee what you are testing for (support of those standards), then it's not a very good test anyway.
Edited 2008-03-27 02:47 UTC





Member since:
2006-01-17
It's still in beta stage, so they still have a chance to fix it (and maybe become a first official browser that passes acid3).
OTOH, tuning specifically for the test doesn't mean that implementation of those features is robust (and that problems won't be visible elsewhere).