mirror of
https://github.com/LadybirdBrowser/ladybird.git
synced 2025-10-22 16:09:23 +00:00
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
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.
17 lines
445 B
HTML
17 lines
445 B
HTML
<!doctype html>
|
|
<link rel="match" href="../expected/svg-path-offset-rounding-ref.html" />
|
|
<meta name="fuzzy" content="maxDifference=0-1;totalPixels=0-1">
|
|
<style>
|
|
body {
|
|
padding-left: 10.6px;
|
|
}
|
|
</style>
|
|
<body>
|
|
<svg width="34" height="22" viewBox="0 0 34 22">
|
|
<path
|
|
d="M -0.2 0 L 34 0 L 34 22 L -0.2 22 Z"
|
|
fill="none"
|
|
stroke="#000000"
|
|
></path>
|
|
</svg>
|
|
</body>
|