Also, he actually did work on web browsers previously:

> Until that point, my career had been focused on web browsers (WebKit at Apple & Nokia).

So he knows exactly what he's doing.

Based on those two datapoints, I'd say he (and other contributors) have a good shot at it.

[0] https://www.ekioh.com/flow-browser/ [1] https://www.ekioh.com/devblog/acid/

Yes, I do disqualify it for that reason.

> Coincidence or not, that's a great date.

Especially if considering that St. Ulrich is also the saint of the dying.

Acid2 was specifically built to call IE out and to put browser builders on notice. It tests the most nuanced little quirks of some specific specs; and, because of some changes in the modern standard, doesn’t actually conform anymore.

This is with all extensions off using Firefox ESR

https://imgur.com/a/ExBMzlx

Disabling the LastPass add-on brought it to 100%. I'm guessing you also use LastPass?

Though I suppose rendering differences that affect z-order or visibility could be detected indirectly, by listening for pointer events on elements that are "supposed to be" visible/hidden.

edit: MacOS and Windows.

On FF for Android it hits 100% but the image is incorrect (there is red text in the top-left).

Same (FF 104.0.2 on Mac, with uBO).

The failing test is:

    Test 64 failed: object.data isn't absolute

Yes, I am aware also that HN has blindspots, eg with Show HN Dropbox

> 1708 Battle of Holowczyn: Swedish King Charles XII defeats superior Russian force in surprising vctory

That must have been it.

Not entirely!

https://en.wikipedia.org/wiki/Rebild_Festival

I’m not American by the way.

Relatedly, I find that with regards to history, most people have quite a large recency bias. If I ask someone who the greatest actors of all time are, at least half will be within the last several years. Same with this question, the first non imperialist great power is likely some random Chinese or Mesopotamian or African kingdom.

https://en.m.wikipedia.org/wiki/Tir_(month)#Observances:

“Independence Day (United States) - 14 or 15 Tir”

I'm talking about easy stuff, too, like normal flow, margin, border, padding box alignment.

The existing official test suites are entirely manual.

Edit: What you're describing requires you to make the entire world first, then finally test something.

Here's an example: I want to test the white-space property. How do I test that? Oh also, font rasterizers are all different and standards don't dictate what happens after box layout. It's acceptable that glyphs render with different dimensions.

How do I test that? A casual HN reader isn't going to care. Someone actually writing this stuff, will.

Rather, those acid tests were tests that test the rendering engine (in multiple aspects at the same time), and are meant for the end users: to give them a nice visual representation of the browser's progress, or lack thereof, and to push browser developers to fix issues that cause visual glitches (with features drawing the test image selected to be nice for layout writers to have) and have them race each other to pass them...

What about W3C's web-platform-tests suite [1]?

[1]: https://github.com/web-platform-tests/wpt/tree/master/css

Do it again with different CSS settings.