ladybird/Tests/LibWeb/Screenshot/input/canvas-shadow.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

33 lines
735 B
HTML

<!DOCTYPE html>
<link rel="match" href="../expected/canvas-shadow-ref.html" />
<meta name="fuzzy" content="maxDifference=0-1;totalPixels=0-809">
<style>
* {
margin: 0;
}
body {
background-color: white;
}
</style>
<canvas width=800 height=600></canvas>
<script>
const canvas = document.querySelector("canvas");
const ctx = canvas.getContext("2d");
// Shadow
ctx.shadowColor = "LightCoral";
ctx.shadowOffsetX = 15;
ctx.shadowOffsetY = 15;
ctx.shadowBlur = 5;
// Filled rectangle
ctx.fillStyle = "red";
ctx.fillRect(20, 10, 100, 100);
// Stroked rectangle
ctx.lineWidth = 4;
ctx.strokeStyle = "red";
ctx.strokeRect(170, 10, 100, 100);
</script>