ladybird/Tests/LibWeb/Screenshot/input/svg-clip-path-transform.html
Jelle Raaijmakers 59a867d3e3
Some checks are pending
CI / Linux, x86_64, Fuzzers, Clang (push) Waiting to run
CI / Linux, x86_64, Sanitizer, GNU (push) Waiting to run
CI / macOS, arm64, Sanitizer, Clang (push) Waiting to run
CI / Linux, x86_64, Sanitizer, Clang (push) Waiting to run
Package the js repl as a binary artifact / Linux, arm64 (push) Waiting to run
Package the js repl as a binary artifact / macOS, arm64 (push) Waiting to run
Package the js repl as a binary artifact / Linux, x86_64 (push) Waiting to run
Run test262 and test-wasm / run_and_update_results (push) Waiting to run
Lint Code / lint (push) Waiting to run
Label PRs with merge conflicts / auto-labeler (push) Waiting to run
Push notes / build (push) Waiting to run
Tests: Enable all screenshot tests on all platforms
With the newly supported fuzzy matching in our test-web runner, we can
now define the expected maximum color channel and pixel count errors per
failing test and set a baseline they should not exceed.

The figures I added to these tests all come from my macOS M4 machine.
Most discrepancies seem to come from color calculations being slightly
off.
2025-07-17 12:59:11 +01:00

22 lines
959 B
HTML

<!DOCTYPE html>
<link rel="match" href="../expected/svg-clip-path-transform-ref.html" />
<meta name="fuzzy" content="maxDifference=0-1;totalPixels=0-5">
<svg>
<g id="root" transform="scale(.5 .5)">
<g id="maskContainer" transform="scale(.5 2)">
<clipPath id="maskGroup" transform="translate(0,20)">
<path id="maskPath" d="M0 0h100v100H0z" />
</clipPath>
</g>
<g id="targetContainer" transform="rotate(5)">
<g transform="translate(20,0)">
<path d="M0 0h100v100H0z" style="fill:red" />
<path d="M0 100h100v100H0z" style="fill:red" />
</g>
<g id="targetGroup" clip-path="url(#maskGroup)" transform="translate(20,0)">
<path id="targetPath1" d="M0 0h100v100H0z" style="fill:green" />
<path id="targetPath2" d="M0 100h100v100H0z" style="fill:blue" />
</g>
</g>
</g>
</svg>