The WPT test transform3d-sorting-006.html gainedthea fairly-generous fuzzy annotation ` <meta name=fuzzy content="0-100;0-500">` a few months ago, to make it pass in Chromium, here (merged to our tree in bug 1715894): https://github.com/web-platform-tests/wpt/commit/47390a2d7a51364a5124abfff92f2dd7a6bd8a6f As it turns out, Firefox *also* has some fuzzy mismatches on this test, slightly more than Chromium does -- we have 544 fuzzy pixels (rather than 500) with a maxDifference of 162 (rather than 100), at least on my Linux machine. However, all of the fuzzy pixels are in the antialiased fringes of transformed shapes -- the overall stacking order is correct, which is what the test seems to be getting at. Given that the test already has a built-in fuzzy annotation which is sufficient for Chromium but not-quite-sufficient for Firefox, it seems like we should adjust that annotation to make it accommodate Firefox's level of antialiasing fuzziness. This test is included in the compat2021 list, BTW; hence, I'm marking this as blocking that metabug.
Bug 1737884 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
The WPT test transform3d-sorting-006.html gained a fairly-generous fuzzy annotation `<meta name=fuzzy content="0-100;0-500">` a few months ago, to make it pass in Chromium, here (merged to our tree in bug 1715894): https://github.com/web-platform-tests/wpt/commit/47390a2d7a51364a5124abfff92f2dd7a6bd8a6f As it turns out, Firefox *also* has some fuzzy mismatches on this test, slightly more than Chromium does -- we have 544 fuzzy pixels (rather than 500) with a maxDifference of 162 (rather than 100), at least on my Linux machine. However, all of the fuzzy pixels are in the antialiased fringes of transformed shapes -- the overall stacking order is correct, which is what the test seems to be getting at. Given that the test already has a built-in fuzzy annotation which is sufficient for Chromium but not-quite-sufficient for Firefox, it seems like we should adjust that annotation to make it accommodate Firefox's level of antialiasing fuzziness. This test is included in the compat2021 list, BTW; hence, I'm marking this as blocking that metabug.