[Gecko Bug 1702398] Use Ahem font in WPT 'align-items-baseline-overflow-non-visible.html' to avoid fuzzy failures from clipped antialiased fringe. #28336
In this WPT test, the testcase has an 'overflow:hidden' container, while the
This patch addresses the issue by switching to the Ahem font, which is simpler
Differential Revision: https://phabricator.services.mozilla.com/D110510
… to avoid fuzzy failures from clipped antialiased fringe. In this WPT test, the testcase has an 'overflow:hidden' container, while the reference case does not. The test fails on some platforms because the "Y" character has some antialiased fringe that bleeds imperceptibly past the content-box, and gets clipped in the testcase but not in the reference case. (This behavior is entirely allowable, and it shouldn't result in a test failure. It's also unrelated to the behavior that the baseline-alignment behavior that the test is trying to exercise.) This patch addresses the issue by switching to the Ahem font, which is simpler and less likely to have antialiasing fringe that would be clipped in this way. I'm using the 25px/1 suggested styling from the documentation at https://web-platform-tests.org/writing-tests/ahem.html Differential Revision: https://phabricator.services.mozilla.com/D110510 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1702398 gecko-commit: f8079fe8757e972b6ebee42dcd4c940c50042289 gecko-reviewers: emilio
Looks like an infra issue of some sort. @jgraham do you know if we can retrigger that task, or what the right thing to do is here?
Looks like that sort-of worked -- this now shows "all checks have passed" as the status, with a "Squash and merge" button that's available to me but which I'm hesitant to press without knowing if automation is supposed to do that part for me & is just pending for some reason. :)