HTML5test VS The Acid3 Test

I just don't know what else I can do. I compared Chromium and Firefox in html5test.com, got same result. All browsers says they doesn't support H.265. I turned off HW acceleration, nothing changes. I installed ffmpeg-libs and other codecs from Fedora wiki. Nothing changes. Videos are same vp9 in browsers. I spent all day googling but nothing helpful. Source: 5 months ago

What does https://html5test.com/ say for h.264, VP8, VP9 and Theora support? What does it say for aac, Opus, Vorbis and mp3 support? Source: 5 months ago

You can use this website also https://html5test.com is really helpful with more datails. Source: 6 months ago

If I go on html5test.com, no matter which browser I use, H265 support is not enabled and I couldn't find any article online that explains why -- what am I missing here? Source: 8 months ago

When I install Opera via flatpak and do html 5 test it says h264 is not supported, what can I do? Source: 12 months ago

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

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

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

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

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