Hacker News Reader

Comment by stolenmerch | Hacker News Reader

I don't follow web standards closely, but I'm curious if this comment is still true (or was ever true): "For people who don't follow modern web standards, a modern web browser getting 100/100 is actually failing tests. You should get 97/100, failing tests 23, 25, and 35."

https://news.ycombinator.com/item?id=18941348

View on HN

The old version (http://acid3.acidtests.org/) will reach 97/100 on modern compliant browsers. There is a newer version (https://wpt.live/acid/acid3/test.html) which incorporates the changes made to the specs in the meantime, so modern browsers will reach 100/100 on this one again. The test was carried out against this version, as you can see in the address bar in the screenshot.

Hmm, I'm seeing 99/100 in Chromium (mobile and desktop). I wonder what test is failing.

It says "test 64 is failing: object.data isn't absolute"

Chrome is just abiding by the much more important industry standard of "it has to work in chrome, period"

Have you tried http:// instead of https://?

Passing the individual tests is only part of passing the complete test. Animations must be smooth and everything must be rendered pixel perfect to the sample image. All Chromium based browsers, I tried Chrome Chromium, Edge and Vivaldi appear to fail the test even if they get a 100/100 score. They all display a thin red line near the upper right of the white box. This line doesn't appear on the sample image.

Do your displays have non-integer scaling enabled?

Your link also only gets 99/100 on modern browsers.

Why? Well...

    // test 64: more attribute tests
    // attributes of the <object> element
    var obj1 = document.createElement('object');
    obj1.setAttribute('data', 'test.html');
    // ...
    assert(obj1.data.match(/^http:/), "object.data isn't absolute");

See that "http" in test 64? Turns out you'll get a score of 100/100 if you use the http version of the URL instead of HTTPS.

Confirmed for me. Where's the metatest that tests Acid3?

Right here, it seems :)

Interesting, by forcing http I get 100/100 with chrome on windows but the animation is not smooth (there is a pause at 69/100) and it definitely does not match the reference image (there are no colored boxes at all).

I got either 68, 97 or 99 on Safari iOS. Disabled content blockers and Darker Reader.

I was seeing the same untill I changed the urls to http rather than https as per another comment, then it gets 100.

The animation is far from being fluid too.

There's an up to date version following modern specs linked in the twitter thread:

https://twitter.com/OrphisFlo/status/1508954585993461763 http://wpt.live/acid/acid3/test.html

That's correct. Tests 23 & 25 require a specific error type that has since been changed in that circumstance: https://github.com/whatwg/dom/issues/319#ref-commit-94dd371

Test 35 requires root elements to not match :first-child, and the spec was changed to specify that they should match: https://bugzilla.mozilla.org/show_bug.cgi?id=1300374

That's pretty dumb grading. Why not flip the sense of the assert for those three tests?

It's useful for statements like "Firefox 2.0 got 82/100 on the Acid3 test" to have truth-values that don't change over time. The Acid3 test is an important part of the history of the Web, and rewriting history is repugnant.

I meant why was it ever like that?

Its author, Hixie, was only one of the people who decided on web standards, and he didn't win every argument, so some of the behavior that eventually got standardized wasn't the behavior Hixie thought was best at the time he wrote Acid3. He did win most of the arguments by virtue of writing the HTML5 spec, but without the buy-in of browser implementors HTML5 would have been irrelevant. Also sometimes he was wrong about things.

Reply on news.ycombinator.com