4 ms·
On my machine: Chromium 71: 97%, blocks 2&3 silver, pauses at 24, 64. Firefox Quantum 64: 97%, blocks 2&3 silver, pauses at 24, 64, 65. From Wikipedia: Buck
by sonofgod 8y ago
On my machine:
Chromium 71: 97%, blocks 2&3 silver, pauses at 24, 64.
Firefox Quantum 64: 97%, blocks 2&3 silver, pauses at 24, 64, 65.
From Wikipedia:
Bucket 2: DOM2 Core and DOM Events
Bucket 3: DOM2 Views, DOM 2 Style, CSS3 selectors and Media Queries
By April 2017, the updated specifications had diverged from the test such that the latest versions of Google Chrome 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."
- msla 8y agoAs I recall, the Firefox of the time didn't pass Acid3, either, and there was a minor controversy over the fact they changed the test in a way that made it friendlier to Firefox: https://en.wikipedia.org/wiki/Acid3 https://en.wikipedia.org/wiki/Acid3 > Initially, Firefox 4 scored 97/100, because it did not support SVG fonts. Later, Firefox 4 scored 100/100, because the SVG font tests were removed from Acid3. > According to Mozilla employee Robert O'Callahan, Firefox did not support SVG fonts because Mozilla considered WOFF a superior alternative to SVG fonts.[29] Another Mozilla engineer, Boris Zbarsky, claimed that the subset of the specification implemented in Webkit and Opera gives no benefits to web authors or users over WOFF, and he asserted that implementing SVG Fonts fully in a web browser is hard because it was "not designed with integration with HTML in mind".[30]