3 ms·
It's a great achievement! But note that it doesn't mean that the browser interprets modern CSS correctly. Wikipedia's Acid3 page says: > By April 2017, the u
by Tomte 5y ago
It's a great achievement!
But note that it doesn't mean that the browser interprets modern CSS correctly.
Wikipedia's Acid3 page says:
> 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. Hickson acknowledges that some aspects of the test were controversial and has written that the test "no longer reflects the consensus of the Web standards it purports to test, especially when it comes to issues affecting mobile browsers".
Strangly, my Safari on iPad just achieved 100/100. a minute ago it achieved 97/100.
Does anyone know what's up with it? Are there timing dependencies? What are the divergences in modern specifications?
- gnarbarian 5y agoThat's how fast web standards change. Try again it'll probably be 95. I'm joking of course. The things /I/ want [1] seem to take forever to get proper support. https://www.w3.org/TR/webgpu/ https://www.w3.org/TR/webgpu/
- sebzim4500 5y agoHave you tried being a multi billion dollar company? The things Google wants seem to be added pretty quickly.
- nightpool 5y agoI don't know what the divergences are specifically, but there's an up to date version following modern specs that's linked in the twitter thread, that's what the screenshot is of: https://twitter.com/OrphisFlo/status/1508954585993461763 https://twitter.com/OrphisFlo/status/1508954585993461763 http://wpt.live/acid/acid3/test.html http://wpt.live/acid/acid3/test.html
- jug 5y agoIIRC it's something about timings that makes it fluctuate. At 97+ or so a browser can in fact be compliant insofar as the test goes.
- girvo 5y agoThis test, as per the address bar in the screenshot, uses the newer Acid3 test that is 100/100 (provided you access the http not https version) in modern browsers, though, not the older one.