BrowseEmAll VS The Acid3 Test

BrowseEmAll mentions (0)

The Acid3 Test mentions (5)

• Shadow: New browser engine made almost in JavaScript

  Https://shadow.goose.icu/?http://acid3.acidtests.org/. - Source: Hacker News / 7 months ago

• Should there be a standard prompt for showcasing models?

  During the browser wars, web developers created “Acid Tests” to see how well a browser supported various style sheet and markup conventions. When the acid tests became popular, there were accusations that browser engineers were manipulating their rendering engines to pass those tests. For instance, some cascading style sheet attribute would pass the test, but fail to work as expected under normal use on a web page. Source: about 1 year ago

• Everyone should use Firefox

  I am sure that both firefox and chromium-based browsers will pass most of something like ACID3 test. But at this stage standards have nothing to do with reality. Standards define perhaps 10% of the code you are writing and interpretation of the rest 90% of the code is up to the browsers. Source: almost 2 years ago

• SerenityOS Browser now passes the Acid3 test

  The old version (http://acid3.acidtests.org/) will reach 97/100 on modern compliant browsers. There is a newer version (https://wpt.live/acid/acid3/test.html) which incorporates the changes made to the specs in the meantime, so modern browsers will reach 100/100 on this one again. The test was carried out against this version, as you can see in the address bar in the screenshot. - Source: Hacker News / about 2 years ago

• "You don't deserve to have a job!" Debatable, but you're still wrong.

  Different PRESENTATION of content on mobile is good. Different content on mobile is the definition of r/assholedesign. It does not matter if the http user agent is a "good" one or not, it should just work. There is a specification, numerous accessibility guidelines, plenty of tests and benchmarks. This isn't 1999 anymore... 🤷‍♂️. Source: over 2 years ago