Jump to content

Acid3

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Pboyd04 (talk | contribs) at 17:52, 26 February 2011 (→‎Mobile browsers). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Acid3
The "reference rendering" for Acid3
Type of site
Web standards test
Available inEnglish language
OwnerThe Web Standards Project
Created byIan Hickson
URLacid3.acidtests.org
Commercialno
Registrationno

Acid3 test is a web test page which can be found at acid3.acidtests.org from the Web Standards Project that checks the performance of a web browser regarding the issue of following certain selected elements from web standards, especially relating to the Document Object Model (DOM) and JavaScript.

If the test is successful, the results of the Acid3 test will display a gradually increasing percentage counter with colored rectangles in the background. The number of subtests passed will indicate the percentage that will be displayed on the screen. This percentage does not represent an actual percentage of conformance as the test does not really keep track of the subtests that were actually started (100 is assumed). Moreover, the browser also has to render the page exactly as the reference page is rendered in the same browser. Like the text of the Acid2 test, the text of the Acid3 reference rendering is not a bitmap, in order to allow for certain differences in font rendering.

Acid3 was in development from April 2007,[1] and released on 3 March 2008.[2] The main developer was Ian Hickson, a Google employee who also wrote the Acid2 test. Acid2 focused primarily on Cascading Style Sheets (CSS), but this third Acid test also focuses on technologies used on modern, highly interactive websites characteristic of Web 2.0, such as ECMAScript and DOM Level 2. A few subtests also concern Scalable Vector Graphics (SVG), Extensible Markup Language (XML), and data URIs. Controversially, it includes several elements from the CSS2 recommendation that were later removed in CSS2.1 but reintroduced in World Wide Web Consortium (W3C) CSS3 working drafts that have not made it to candidate recommendations yet.

The test

The main part of Acid3 is written in ECMAScript (JavaScript) and consists of 100 subtests in six groups called “buckets”, including four special subtests (0, 97, 98, and 99).[3]

  • Bucket 1: DOM Traversal, DOM Range, HTTP
  • Bucket 2: DOM2 Core and DOM2 Events
  • Bucket 3: DOM2 Views, DOM2 Style, CSS 3 selectors and Media Queries[4]
  • Bucket 4: Behavior of HTML tables and forms when manipulated by script and DOM2 HTML
  • Bucket 5: Tests from the Acid3 Competition (SVG,[5] HTML, SMIL, Unicode, …)
  • Bucket 6: ECMAScript

The compliance criteria require that the test is run with a browser's default settings. The final rendering must have a 100/100 score and must be pixel-identical with the reference rendering.[6] On browsers designed for personal computers, the animation has to be smooth (taking no more than 33 ms for each subtest on reference hardware equivalent to a top-of-the-line Apple laptop) as well,[7] though slower performance on a slow device does not imply non-conformance.[8]

Acid3 rendered by Fennec 1.0 alpha 1. Buckets 2, 4, and 6 pass all 16 subtests, buckets 1 and 3 pass more than 10 subtests while bucket 5 passes more than 5 subtests.

To pass the test the browser must also display a generic favicon in the browser toolbar, not the favicon image from the Acid3 web server. The Acid3 server when asked for favicon.ico gives a 404 response code but with image data in the body. This tests that the web browser correctly handles the 404 error code when fetching the favicon, by treating this as a failure and displaying the generic icon instead.[9]

When the test is running, the rectangles will be added to the rendered image; the number of subtests passed in the bucket will determine the color of the rectangles.

  • 0 subtests passed: No rectangle shown.
  • 1–5 subtests passed: Black rectangle.
  • 6–10 subtests passed: Grey rectangle.
  • 11–15 subtests passed: Silver rectangle.
  • All 16 subtests passed: Colored rectangle (left to right: red, orange, yellow, lime, blue, purple).

Note that Acid3 does not display exactly how many subtests passed in a bucket. For example, 3 subtests passing and 4 subtests passing in bucket 2 would both render a black rectangle.

Detailed results

After the Acid3 test page is completely rendered, the capital A in the word Acid3 can be clicked to see an alert (or shift-click for a new window) explaining exactly which subtests have failed and what the error message was. In case some of the 100 tests passed but took too much time, the report includes timing results for that single test. The alert reports the total time of the whole Acid3 test.

Acid3 rendered by Firefox 3.6. 94/100, test failed.
Acid3 rendered by Internet Explorer 8.0. 20/100, test failed.
Internet Explorer 9 Beta displaying Acid3 score. 95/100, test failed.
Acid3 rendered by XFCE Midori. 100/100, but test failed.
Acid3 rendered by Safari 4. 100/100 without errors in timing and image, test passed.
File:Googchomepass.png
Google 9 showing Acid3 test result-passed all 80 tests.

In order to render the test correctly, user agents need to implement the CSS 3 Text Shadows and the CSS 2.x Downloadable Fonts specifications, which are currently under consideration by W3C to be standardized. This is required as the test uses a custom TrueType font, called "AcidAhemTest" to cover up a 20x20 red square. Supporting Truetype fonts however is not required by the CSS specification. A browser supporting only OpenType fonts with CFF outlines or Embedded OpenType fonts could support the CSS standard but fail the test in the Acid3 test. The glyph, when rendered by the downloaded font, is just a square, made white with CSS, and thus invisible.[10]

In addition, the test also uses Base64 encoded images, some more advanced selectors, CSS 3 color values (HSLA) as well as bogus selectors and values that should be ignored.

Development and impact

Ian Hickson started working on the test in April 2007, but development progressed slowly. In December 2007, work restarted and the project received public attention on 10 January 2008, when it was mentioned in blogs by Anne van Kesteren.[11] At the time the project resided at a URL clearly showing its experimental nature: "http://www.hixie.ch/tests/evil/acid/003/NOT_READY_PLEASE_DO_NOT_USE.html" That notice did not stop the test from receiving widespread attention within the web development community. At that time only 84 subtests had been done, and on 14 January Ian Hickson announced a competition to fill in the missing 16.[12]

The following developers contributed to the final test through this competition:

  • Sylvain Pasche: subtests 66 and 67: DOM.
  • David Chan: subtest 68: UTF-16/UCS-2.
  • Simon Pieters (Opera) and Anne van Kesteren (Opera): subtest 71: HTML parsing.
  • Jonas Sicking (Mozilla) and Garrett Smith: subtest 72: dynamic modification of style blocks' text nodes.
  • Jonas Sicking (Mozilla): subtest 73: Nested events.
  • Erik Dahlström (Opera): subtests 74 to 78: SVG and SMIL.
  • Cameron McCormack (Batik SVG library): subtest 79: SVG fonts.

Even before its official release, Acid3's impact on browser development was dramatic. WebKit in particular made progress; in less than a month their score rose from 60 to 87.[13]

The test was officially released on 3 March 2008.[2] A guide and commentary was expected to follow within a few months,[13] but, as of May 2009, it had not yet been released. The announcement that the test is complete means only that it is to be considered "stable enough" for actual use. A few problems and bugs were found with the test, and it was modified to fix them.[14][15] On 26 March 2008—the day both Opera and WebKit teams announced a 100/100 score—developers of WebKit contacted main Acid3 developer Ian Hickson about a critical bug in the Acid3 that presumably may have forced a violation of the SVG 1.1 standard to pass. Hickson proceeded to fix it with the help of Cameron McCormack, member of W3C's SVG Working Group.[16][17]

By the end of March 2008, early development versions of the Presto[18][19] and WebKit[17] layout engines (used by Opera and Safari respectively, among others) scored 100/100 on the test and rendered the test page correctly. At the time, no browser using the Presto or WebKit layout engines passed the performance aspect of the test. On 14 March 2009, Iris Browser 1.1.4, a WebKit-based mobile browser, became the first public release of a web browser to pass Acid3,[20][21][failed verification] and on 7 June, iCab 4.6 for Mac OS X was unofficially announced as the first official release of a desktop browser to pass the test;[22][23][failed verification] Safari 4, also based on WebKit, passed the next day,[24][failed verification] although a development version had already passed the previous September.[25][26] By October, Epiphany, another WebKit-based browser, also passed.[27][failed verification] In May and June, Google Chrome 2.0[citation needed] and Opera Mobile 9.7 beta[28] displayed a score of 100/100, but did not actually pass; release versions of these browsers passed fully later in the year.[citation needed][29] Security concerns over downloadable fonts delayed Chrome from passing.[30]

At the time of Acid3's release, Mozilla Firefox developers had been preparing for the imminent release of Firefox 3, focusing more on stability than Acid3 success. The resulting 3.0 release consequently gained a score of 71.[31] The performance of Firefox was improved in version 3.5, which scores 93/100, and version 3.6, which scores 94/100. Firefox 4 scores 97/100 because it does not support SVG fonts. According to Mozilla employee Robert O'Callahan, Firefox does not support SVG fonts because Mozilla considers WOFF a superior alternative to SVG fonts.[32] Another Mozilla engineer Boris Zbarsky agrees that the subset of the specification implemented in Webkit and Opera gives no benefits to web authors or users over WOFF, and claims implementing SVG Fonts fully in a web browser is hard because it was "not designed with integration with HTML in mind"[33]

Microsoft, developers of the Internet Explorer (IE) browser, said that Acid3 does not map to the goal of Internet Explorer 8 and that IE8 would improve only some of the standards being tested by Acid3.[34] IE8 scores 20/100, which is much worse than all relevant competitors in their versions from the test's release, and has some problems with rendering the Acid3 test page. On 18 November 2009, the Internet Explorer team posted a blog entry about the early development of Internet Explorer 9 from the PDC presentation, showing that an internal build of the browser could score 32/100 for the Acid3 test.[35]

On 2 April 2010, Ian Hickson made minor changes to the test after Mozilla, due to privacy concerns, altered the way Gecko handles the :visited pseudo-class.[36][37]

Throughout 2010, several public Developer Previews gradually improved Internet Explorer 9's test scores from 55/100 (on 16 March[38]) to 95/100 (as of 4 August).[39][40][41] General Manager of the IE team Dean Hachamovich argues that striving for 100/100 on the Acid3 test isn't necessary or desirable. He claims the two Acid3 failures are on features (SVG fonts and SMIL animation) that are "in transition".[42]

Criticism

The current iteration of the test has been criticized for being a cherry-picked collection of features that are rarely used, as well as those that are still in a W3C working draft. Eric Meyer, a notable web standards advocate, writes, "The real point here is that the Acid3 test isn't a broad-spectrum standards-support test. It's a showpiece, and something of a Potemkin village at that. Which is a shame, because what's really needed right now is exhaustive test suites for specifications– XHTML, CSS, DOM, SVG."[43]

"Implementing just enough of the standard to pass a test is disingenuous, and has nothing to do with standards compliance," argues Mozilla UX lead Alex Limi, in his article "Mythbusting: Why Firefox 4 won’t score 100 on Acid3." Limi argues that some of the tests, particularly those for SVG fonts, have no relation to real usage, and implementations in some browsers are created solely for the point of raising scores.[44]

Standards tested

Parts of the following standards are tested by Acid3:

  • HTTP 1.1 Protocol
  • DOM Level 2 Views
  • HTML 4.01 Strict
  • DOM Level 2 Traversal (subtests 1–6)
  • DOM Level 2 Range (subtests 7–11)
  • Content-Type: image/png; text/plain (subtests 14–15)
  • <object> handling and HTTP status codes (subtest 16)
  • DOM Level 2 Core (subtests 17, 21)
  • ECMAScript GC (subtests 26–27)
  • DOM Level 2 Events (subtests 17, 30–32)
  • CSS Selectors (subtests 33–40)
  • DOM Level 2 Style (subtest 45)
  • DOM Level 2 HTML (subtest 60)
  • Unicode 5.0 UTF-16 (subtest 68)
  • Unicode 5.0 UTF-8 (subtest 70)
  • HTML 4.0 Transitional (subtest 71)
  • SVG 1.1 (subtests 74, 78)
  • SMIL 2.1 (subtests 75–76)
  • SVG 1.1 Fonts (subtests 77, 79)
  • ECMAScript Conformance (subtests 81-96)
  • Data URI scheme (subtest 97)
  • XHTML 1.0 Strict (subtest 98)

Passing conditions

A passing score is only considered valid if the browser's default settings were used.

The following browser settings and user actions may invalidate the test:

  • Zooming in or out
  • Disabling images
  • Applying custom fonts, colors, styles, etc.
  • Having add-ons or extensions installed and enabled
  • Installed and enabled User JavaScript or Greasemonkey scripts

Browsers that pass

Note that only stable, public releases are listed here (alpha and beta versions, for example, would not qualify).

Desktop browsers

Template:WebSlice-begin

Layout engine Browser Release date Latest stable release version date Rendering Performance
WebKit Google Chrome 4.0.249.78[45] January 25, 2010
Windows, macOS, Linux126.0.6478.61/62[46] Edit this on Wikidata / 13 June 2024; 2 days ago (13 June 2024)
Windows Server 2012/2012 R2109.0.5414.165[47] / 13 September 2023; 9 months ago (2023-09-13)
Android126.4.6478.71[48] Edit this on Wikidata / 13 June 2024; 2 days ago (13 June 2024)
iOS126.0.6478.54[49] Edit this on Wikidata / 11 June 2024; 4 days ago (11 June 2024)
Extended Support Release126.0.6478.56/57[50] Edit this on Wikidata / 11 June 2024; 4 days ago (11 June 2024)
 Yes Yes
WebKit Safari 4.0[51][52] June 8, 2009 Template:Latest stable software release/Safari Yes Yes[53]
Presto Opera 10[29] September 1, 2009 100.0.4815.21 (June 20, 2023; 11 months ago (2023-06-20)[54][55][56])


Yes ?
WebKit Epiphany 2.28.0[57] October 2, 2009 Template:Latest stable software release/Epiphany Yes[citation needed] ?

Template:WebSlice-end

Mobile browsers

Note: For mobile browsers it is not possible to consider the "performance" portion of the test, as mobile browsers cannot be run on the reference hardware.

Template:WebSlice-begin

Layout engine Browser Release date Latest stable release version date Rendering
WebKit Iris Browser 1.1.4[20] March 14, 2009 1.1.9 (July 6, 2009; 14 years ago (2009-07-06)) [±] Yes
WebKit Bolt browser 1.6[58] December 7, 2009 2.52 [±] Yes
Presto Opera Mobile 9.7[28] March 26, 2009 Template:Latest stable software release/Opera Mobile Yes
WebKit Android Browser 3.0 February 26, 2011 3.0 Yes

Template:WebSlice-end

Other browsers

Template:WebSlice-begin

Layout engine Browser Release date Latest stable release version date Rendering Performance
WebKit Google Earth 5.2.1.1329[citation needed] June 14, 2010
Pro (Linux, macOS, and Windows)7.3.6.9796 / February 22, 2024; 3 months ago (2024-02-22)[59][60]
Android10.46.0.2 / January 25, 2024; 4 months ago (2024-01-25)[61]
iOS10.52.1 / April 15, 2024; 2 months ago (2024-04-15)[62]
Web App10.52.0.0[63]


 Yes ?

Template:WebSlice-end

Browsers that do not pass

Acid3 was deliberately written in such a way that every web browser failed the test at the time of its release. Many of the browser teams are actively working to improve test results. Other browser makers consider parts of the Acid3 test such as SVG fonts to now be irrelevant because WOFF will soon be supported by all major browsers.[64] Mozilla and possibly other browser makers intend to only complete the parts of Acid3 that aren't related to the outdated SVG fonts standards.

Desktop browsers

Template:WebSlice-begin

Desktop browser progress for the Acid3 test
Layout engine Browser Screenshot of a current release Screenshot of a preview release
Gecko Mozilla Firefox
94/100
Mozilla Firefox 3.6.13
97/100
Mozilla Firefox 4.0b9pre [65][66][67]
KHTML Konqueror
89/100
Konqueror 4.5.3[68] 		none
Trident Internet Explorer
20/100
Internet Explorer 8.0
95/100
Internet Explorer 9 RC, 9.0.8080.16413 [69]

Template:WebSlice-end

Mobile browsers

Template:WebSlice-begin

Mobile layout engine progress for the Acid3 test
Layout engine Major browsers Screenshot of current release Screenshot of preview release
WebKit Android browser
93/100
Android 2.3 		None
BlackBerry Browser
100/100 but incorrect rendering
BlackBerry OS 6 		None
Dolphin Browser
98/100
bada OS 1.0.2 		None
Mobile Safari
100/100 but incorrect rendering
Mobile Safari 4.0 		None
Nokia Mini Map Browser
47/100
S60 5th Edition 		None
Skyfire File:IOS SkyFire 2 Acid3.png
100/100 but incorrect rendering
Skyfire 2.0 		None
webOS browser File:Acid3-webos.png
92/100
webOS 1.4 		None
Presto Opera Mini
98/100
Opera Mini 5 		None
Gecko Firefox for mobile
94/100
Firefox 1.1 for Maemo
97/100
Firefox 4 Beta 2 for Mobile
MicroB 94/100 None
Trident Internet Explorer Mobile
12/100
Internet Explorer Mobile 7 		None

Template:WebSlice-end

Console browsers

Template:WebSlice-begin

Acid3 compliance in game console web browsers
Layout engine Major browsers Screenshot of current release Screenshot of preview release
NetFront PlayStation 3 browser
27/100
PS3 Firmware 3.10 		None
PSP Browser
11/100
NetFront 3.5 		None
Presto Wii Internet Channel
40/100
21 June 2010 update
Browser crashes after test 		None
Nintendo DSi Browser
59/100
None

Template:WebSlice-end

Other browsers

Template:WebSlice-begin

Acid3 compliance in other web browsers
Layout engine Major browsers Screenshot of current release Screenshot of preview release
Webkit Dreamweaver Live View File:Dreamweaver CS5 acid3.png
90/100
Dreamweaver CS5 		None
Second Life browser
100/100
Second Life 2.0 		None
Steam in-game browser File:SteamAcid3.jpg
100/100
Steam 2010 UI Update 		None

Template:WebSlice-end

See also

References

  1. ^ "HTML5 IRC logs: freenode / #whatwg / 20070422". 23 April 2007. Retrieved 2007-12-28.
  2. ^ a b "Acid3: Putting Browser Makers on Notice, Again" (Press release). Web Standards Project. 2008-03-03. Retrieved 2007-03-04.
  3. ^ Hickson, Ian (2008-03-03). "Comments in the source code of the test page". Web Standards Project. Retrieved 2008-02-16.
  4. ^ Lie, Håkon Wium (15 September 2009). "Media Queries". World Wide Web Consortium. Retrieved 9 February 2010. {{cite web}}: Unknown parameter |coauthors= ignored (|author= suggested) (help)
  5. ^ Dahlström, Erik (2008-01-22). "Getting to the core of the web". Opera Software. Retrieved 2008-02-16.
  6. ^ Hickson, Ian. "The Acid3 Test (reference Rendering)". Web Standards Project. Retrieved 9 February 2010.
  7. ^ Ian Hickson (2008-04-01). "The performance aspect of Acid3". Retrieved 2008-04-03.
  8. ^ "Acid3 Browser Test - The Web Standards Project". Web Standards Project. Retrieved 9 February 2010.
  9. ^ Maciej Stachowiak (2008-09-26). "comment to 'Full pass of Acid3'". WebKit.org. Retrieved 2009-04-29.
  10. ^ Hickson, Ian (2008-03-29). "The antialiasing controversy in Acid3". Retrieved 2009-04-30.
  11. ^ van Kesteren, Anne (2008-01-10). "Acid3". Retrieved 2008-03-04.
  12. ^ Hickson, Ian (2008-01-14). "The competition for you to come up with the best test for Acid3". Retrieved 2008-03-04.
  13. ^ a b Hickson, Ian (2008-03-04). "Moebius (announcement of the completion of the test)". Retrieved 2008-03-04.
  14. ^ Ian Hickson. "Tests that are never quite finished". Retrieved 2008-03-30.
  15. ^ Ian Hickson (2008-04-22). "Media queries and performance in Acid3 (and an error on my part)". Retrieved 2008-04-24.
  16. ^ Ian Hickson. "Last minute changes to Acid3". Retrieved 2008-03-30.
  17. ^ a b Maciej Stachowiak (2008-03-26). "WebKit achieves Acid3 100/100 in public build". WebKit.org. Retrieved 2008-03-26.
  18. ^ Tim Altman (March 2008). "Opera and the Acid3 Test". Opera Software. Retrieved 2008-03-28.
  19. ^ Lars Erik Bolstad (March 2008). "Public Acid3 build". Opera Software. Retrieved 2008-03-28. The latest post-9.5 build scores 99/100 and fails the smoothness criterion.
  20. ^ a b Torchmobile.com[dead link]
  21. ^ David K (15 March 2009). "Iris 1.1.4 Released – More Stable and Scroll Support". Fuze Mobility. Retrieved 9 February 2010. [dead link]
  22. ^ Michael, Lankton (28 July 2009). "2009 Mac Web Browser Shootout!". ConnectedInternet.co.uk. Retrieved 9 February 2010.
  23. ^ "iCab 4.6 ships". FairerPlatform.com. 8 June 2009. Retrieved 9 February 2010. [dead link]
  24. ^ Paul Lilly (2008-09-29). "Safari Beta 4 is the First Browser to Hit a Perfect Acid3 Test Score". Maximum PC. Retrieved 2009-11-16.
  25. ^ Peterson, Adele (9 April 2007). "The WebKit browser engine running under the Safari browser UI". WebKit.org. Retrieved 2010-02-09.
  26. ^ Stachowiak, Maciej (25 September 2008). "Full Pass of Acid3". WebKit.org. Retrieved 2010-02-09.
  27. ^ Shane (2 October 2009). "Epiphany". Retrieved 9 February 2010. [dead link]
  28. ^ a b Lund Engebø, Helene (26. March 2009). "Opera Mobile 9.7 with Opera Turbo". Opera Software ASA. Retrieved 2009-07-06. {{cite web}}: Check date values in: |date= (help)
  29. ^ a b "Turbocharge your Web experience with Opera 10" (Press release). Opera Software. 2009-09-01. Retrieved 2009-09-04.
  30. ^ "Issue 231: Acid test 3 fails on chrome". Google. 8 July 2009. Retrieved 9 February 2010.
  31. ^ Mike Shaver (2008-03-27). "The missed opportunity of acid 3". Retrieved 2008-03-30.
  32. ^ Robert O'Callahan (2010-6-3). "Not Implementing Features Is Hard". Retrieved 2010-12-15. {{cite web}}: Check date values in: |date= (help)
  33. ^ Limi, Alexander (2011-01-25). "Mythbusting: Why Firefox 4 won't score 100 on Acid3". Retrieved 2011-01-25.
  34. ^ Chris Wilson (20 March 2008). "Windows Internet Explorer 8 Expert Zone Chat (20 March 2008)". Microsoft. Retrieved 2008-04-15. The ACID3 test is a collection of interesting tests, spread across a large set of standards. Some of those standards will see improvements in IE8 - in fact, IE8 already improves on IE7's score - but we are focused on the most important features and standards to make web developers' lives easier. The Acid3 test does not map directly to that goal.
  35. ^ "An Early Look At IE9 for Developers". Microsoft. 18 November 2009. Retrieved 9 February 2010.
  36. ^ Baron, David (2010-03-09), Preventing attacks on a user's history through CSS :visited selectors, Mozilla, retrieved 2010-04-08
  37. ^ Hickson, Ian (2010-04-02), Acid3 update for :link/:visited privacy changes, retrieved 2010-04-07
  38. ^ The Web Standards Project's Acid3 Test, Microsoft. For IE 9's 1st Developer Preview.
  39. ^ The Web Standards Project's Acid3 Test, Microsoft. For IE 9's 2nd Developer Preview.
  40. ^ The Web Standards Project's Acid3 Test, Microsoft. For IE 9's 3rd Developer Preview.
  41. ^ The Web Standards Project's Acid3 Test, Microsoft. For IE 9's 4th Developer Preview.
  42. ^ "Microsoft releases final IE9 preview, beta due in September". ZDNet. 2010-08-26. Retrieved 2010-11-09.
  43. ^ "Acid Redux". 2008-03-22. Retrieved 2010-03-21.
  44. ^ "Mythbusting: Why Firefox 4 won't score 100 on Acid3". 2011-01-25. Retrieved 2011-01-25.
  45. ^ Laforge, Anthony (2010-01-25). "Stable Channel Update". Google. Retrieved 2010-01-25.
  46. ^ "Stable Channel Update for Desktop". 13 June 2024. Retrieved 14 June 2024.
  47. ^ "Stable Channel Desktop Update". 13 September 2023. Retrieved 14 September 2023.
  48. ^ "Chrome for Android Update". 13 June 2024. Retrieved 14 June 2024.
  49. ^ "Chrome Stable for iOS Update". 11 June 2024. Retrieved 11 June 2024.
  50. ^ "Stable Channel Update for Desktop". 11 June 2024. Retrieved 11 June 2024.
  51. ^ "Safari - 150 features". Apple Inc. Retrieved 2009-09-03.
  52. ^ Gregg Keizer (2008-09-29). "WebKit browser engine aces Acid3 test, stakes claim to No. 1". NetworkWorld. Retrieved 2010-12-10.
  53. ^ Stachowiak, Maciej (2008-09-25). "Full Pass of Acid3". WebKit.org. Retrieved 2009-12-07.
  54. ^ "Thanks for downloading Opera". Opera Norway. Retrieved 21 June 2023.
  55. ^ "Thanks for downloading Opera". Opera Norway. Retrieved 21 June 2023.
  56. ^ "Index of /ftp/pub/opera/desktop/100.0.4815.21/". Opera Norway. Retrieved 21 June 2023.
  57. ^ Paul, Ryan (2009-09-24). "Linux garden gets a new GNOME with version 2.28". Ars Technica. Retrieved 2010-01-04.
  58. ^ James, Scott (2009-12-07). "Bolt Browser gets Updated to Version 1.6 – Brings New Features!". BlackBerrySync. Retrieved 2010-02-09.
  59. ^ "See notes on Google Earth releases". Google Earth Help. Retrieved March 8, 2024.
  60. ^ "PPA: Google Earth". UbuntuUpdates. Retrieved March 8, 2024.
  61. ^ "Google Earth APKs". APKMirror. Retrieved March 8, 2024.
  62. ^ "Google Earth on the App Store". Apple App Store. Retrieved April 17, 2024.
  63. ^ "Google Earth on Web". Google. Retrieved April 17, 2024.
  64. ^ Why Firefox 4 Will Never Pass The Acid3 Test, retrieved 2011-02-01
  65. ^ Sharp, Gavin (2008-01-02). "Bug 410460 (acid3) – Acid3 tracking bug". Mozilla. Retrieved 2010-02-09.
  66. ^ "Public Mozilla Acid3 spreadsheet". Retrieved 2008-10-18. {{cite web}}: Text "publisherGoogle" ignored (help)
  67. ^ "Mythbusting: Why Firefox 4 won't score 100 on Acid3". Retrieved 2011-01-25. {{cite web}}: Text "publisherGoogle" ignored (help)
  68. ^ 2008-01-30, Alex. "Bug 156947: Konqueror 4 fails Acid3 test (filed on 30 January 2008)". KDE. Retrieved 2008-03-02. {{cite web}}: |last= has numeric name (help)
  69. ^ "The Web Standards Project's Acid3 Test". Microsoft. Retrieved 4 September 2010.

External links

Wikimedia Commons has media related to Acid3.

Template:Acid tests

Retrieved from "https://en.wikipedia.org/w/index.php?title=Acid3&oldid=416063675"