This is the talk page for discussing improvements to the Acid3 article. This is not a forum for general discussion of the article's subject. |
Article policies
|
Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
Archives: Index, 1, 2, 3, 4, 5Auto-archiving period: 90 days ![]() |
![]() | This article is rated C-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||||||||
|
![]() | This article links to one or more target anchors that no longer exist.
Please help fix the broken anchors. You can remove this template after fixing the problems. | Reporting errors |
Defunct
editAll three Acid tests originally hosted at acidtests.org are no longer present. Hairy Dude (talk) 17:13, 3 January 2022 (UTC)
- I don't understand what you mean. When I go to http://acid3.acidtests.org/ in my FF browser I get an Acid3 test showing me a result of 97/100. What exact test (or tests) are you missing? — JohnFromPinckney (talk / edits) 20:54, 3 January 2022 (UTC)
Updates and History Classifications
editAll these discussions are nice and dandy when it comes to describe the acidtest3.org web page and its use, but insofar as the results displayed, the "contemporary" explanations at the end of the paragraphs always become antiquated after a few years pass by! For example, stating that "Both IE 11 and Edge pass with 100/100." in 2014 (or whenever) is nowadays (in 2022) ERRONEOUS! For whatever reason, my own Edge shows 97/100, as do most of my other browsers; of course, there may be other reasons why they don't pass with 100/100 but without MORE DETAILS, it's irrelevant to write it like so and only contributes to wikipedia's reputation about subjective and/or inaccurate contents! Someone with more experience and skills than me should remedy to that - and it'd help if the person is also as objective as possible! (I'm just saying...) — Preceding unsigned comment added by AzraelDrums (talk • contribs) 21:08, 21 January 2022 (UTC)
Acid3 successor "WPT"
editThere has been an effort by some W3C and Google folk, from what I gather, to support more recent browser features in the Acid3 test. The test seems to be under a "Web Platform Tests" project (WPT), and is available at http://w3c-test.org/acid/acid3/test.html (HTTP seems to be a requirement for 100/100 instead of HTTPS; browser extensions may mess up results), or alternatively on wpt.live instead of w3c-test.org (as they are mirrors).
Anyway, it might be worth a mention on the article. I'm not sure how it'd be included, though; this article talks about the history of the original Acid3 test, and slapping a mention of the updated version (seemingly by different authors) somewhere feels like it wouldn't belong. This is worsened by the fact that the WPT apparently include other tests beyond the Acid3 test. So, I don't know. The whole of the project might be worthy an article of its own. — Avelludo (Talk / Contribs / Log) 03:02, 30 March 2022 (UTC)
- There's nothing really new in the Acid3 fork: it merely comments out subtests that are no longer correct per current specs. (Very much along the lines of Hixie's 2011 changes.) Why comment them out? Because it means we still run the rest of the test, and thus can notice if anywhere else in the test unexpectedly starts failing.
- https://github.com/web-platform-tests/wpt/commits/master/acid/acid3 gives the full history, which makes this clear.
- The short background here is every browser vendor had essentially done this separately, and having it in a shared location avoids duplication of work or disagreements about which subtests still apply. Gsnedders (talk) 19:14, 11 August 2024 (UTC)
URL is Dead
editThe URL (https://acid3.acidtests.org) returns a site not found error. It looks like the Acid3 test has gone offline Wiichicken (talk) 01:21, 8 August 2024 (UTC)