mirror of
https://github.com/LadybirdBrowser/ladybird.git
synced 2025-10-23 00:19:18 +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.
12 lines
403 B
HTML
12 lines
403 B
HTML
<!DOCTYPE html>
|
|
<link rel="match" href="../expected/opacity-stacking-ref.html" />
|
|
<meta name="fuzzy" content="maxDifference=0-2;totalPixels=0-59533">
|
|
<style>
|
|
body {
|
|
background-color: white;
|
|
}
|
|
</style>
|
|
<svg width="600" viewBox="0 0 150 100" xmlns="http://www.w3.org/2000/svg">
|
|
<circle cx="100" cy="50" r="40" fill="black" opacity="0.3" />
|
|
<circle cx="50" cy="50" r="40" fill="blue" />
|
|
</svg>
|