ladybird/Tests/LibWeb/Screenshot/input/inline-node.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

34 lines
939 B
HTML

<!DOCTYPE html>
<html lang="en">
<head>
<link rel="match" href="../expected/inline-node-ref.html" />
<meta name="fuzzy" content="maxDifference=0-1;totalPixels=0-930">
<meta charset="UTF-8">
<title>Inline Node styling test</title>
<style>
body {
line-height: 200%;
}
.highlight {
background-color: orange;
border-radius: 6px;
}
.bg-highlight {
background: magenta;
color: white;
border-radius: 6px;
}
.br-highlight {
border: 2px solid green;
border-radius: 6px;
box-shadow: 4px 4px 4px darkgreen;
}
</style>
</head>
<body>
Hello world <span class="highlight">this is some text</span> not in a box. <span class="bg-highlight">This text has a background</span> and <span class="br-highlight">this text has a shadow!</span>
</body>
</html>