7 ms·

Modern browsers should no longer score 100 on Acid 3 though. >By April 2017, the updated specifications had diverged from the test such that the latest version

Modern browsers should no longer score 100 on Acid 3 though. >By April 2017, the updated specifications had diverged from the test such that the latest versions of Google Chrome, Safari and Mozilla Firefox no longer pass the test as written

5555watch 2mo ago
Aha, I'm getting 97/100 on Safari
- torgoguys 2mo ago
  96/100 with Brave on Android
  - vee-kay 2mo ago
    [dead]
0gs 2mo ago
hmm. i wonder if any of the stuff they have changed since then is stuff i could legitimate not do without in a browser
assimpleaspossi 2mo ago
Exactly. It's meaningless now and I stopped looking at it a few years before 2017 when I ran a Web dev shop
heisgone 2mo ago
Yes, but considering the goal of his project is a proof of concept, that is, proving this project is possible, acid3 is a good place to start to prove the worth of the project and aiming 100% first make more sense. Tweaks will be needed one way or another to make it equivalent to the big 3.
- munch117 2mo ago
  For a piece of software designed by reading the specs and implementing accordingly, there acid3 would be a good way of demonstrating the quality of the result. But is that what happened? If you pass tests that conflict with the specs, then that implies that the implementation is not based on specs, but on feedback from the test. Which means it may be designed to pass the test, and not much good once you go outside the test examples. I'll extend the benefit of the doubt and say that it's possible that the implementation is based on an older version of specs, one that matches the tests. But it doesn't inspire confidence that all we're shown is a single screenshot and no source code.
gsnedders 2mo ago
https://github.com/web-platform-tests/wpt/commits/master/acid/acid3 https://github.com/web-platform-tests/wpt/commits/master/aci... shows the history of the web-platform-tests copy of WPT, which has mostly followed Hixie’s earlier updates to Acid3 by simply commenting out assertions that no longer match what specs say.

5555watch 2mo ago

Aha, I'm getting 97/100 on Safari

torgoguys 2mo ago
96/100 with Brave on Android
- vee-kay 2mo ago
  [dead]

0gs 2mo ago

hmm. i wonder if any of the stuff they have changed since then is stuff i could legitimate not do without in a browser

assimpleaspossi 2mo ago

Exactly. It's meaningless now and I stopped looking at it a few years before 2017 when I ran a Web dev shop

heisgone 2mo ago

Yes, but considering the goal of his project is a proof of concept, that is, proving this project is possible, acid3 is a good place to start to prove the worth of the project and aiming 100% first make more sense. Tweaks will be needed one way or another to make it equivalent to the big 3.

munch117 2mo ago
For a piece of software designed by reading the specs and implementing accordingly, there acid3 would be a good way of demonstrating the quality of the result. But is that what happened? If you pass tests that conflict with the specs, then that implies that the implementation is not based on specs, but on feedback from the test. Which means it may be designed to pass the test, and not much good once you go outside the test examples. I'll extend the benefit of the doubt and say that it's possible that the implementation is based on an older version of specs, one that matches the tests. But it doesn't inspire confidence that all we're shown is a single screenshot and no source code.

gsnedders 2mo ago

https://github.com/web-platform-tests/wpt/commits/master/acid/acid3 https://github.com/web-platform-tests/wpt/commits/master/aci... shows the history of the web-platform-tests copy of WPT, which has mostly followed Hixie’s earlier updates to Acid3 by simply commenting out assertions that no longer match what specs say.