[web-tests] Fix incorrect fuzziness parameter minimums

jonathan-j-lee · chromium-wpt-export-bot · commit 8a68da27f807 · 2023-10-06T14:28:51.000-07:00
A W(P)T may specify fuzziness parameters as either an inclusive range [min, max], or a single expected value [1] (e.g., `totalPixels=30` means exactly 30 pixels must be different for a test/reference to match). This patch corrects a few tests that mistakenly reject exact matches (i.e., maxDifference = totalPixels = 0) because they specify exact nonzero parameters. WPT unfortunately doesn't interpret this as `0-<N>`, even though this is almost always what we want in practice. `run_web_tests.py` allowed these parameters to land because it ignores fuzzy parameters when the image hashes match exactly. Now, to be consistent with [1] and its implementation in wptrunner, only skip diffing when exact matches are expected. [1]: https://web-platform-tests.org/writing-tests/reftests.html#fuzzy-matching Bug: 1254776 Change-Id: I868e571a891b2a570934d17dd605f42db22a0ddf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4908234 Reviewed-by: Weizhong Xia <weizhong@google.com> Commit-Queue: Jonathan Lee <jonathanjlee@google.com> Cr-Commit-Position: refs/heads/main@{#1206623}
diff --git a/html/semantics/embedded-content/the-img-element/image-compositing-change.html b/html/semantics/embedded-content/the-img-element/image-compositing-change.html
@@ -2,7 +2,7 @@
 <html class="reftest-wait">
 <title>Composited images correctly re-raster when the image and bounds change</title>
 <meta charset="utf-8">
-<meta name=fuzzy content="maxDifference=150;totalPixels=296">
+<meta name=fuzzy content="maxDifference=0-150;totalPixels=0-296">
 <link rel="match" href="image-compositing-change-ref.html"/>
 <link rel="help" href="https://html.spec.whatwg.org/multipage/#the-img-element">
 <style>
