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.
11 lines
447 B
HTML
11 lines
447 B
HTML
<!DOCTYPE html>
|
|
<link rel="match" href="../expected/selection-start-in-end-node-ref.html" />
|
|
<meta name="fuzzy" content="maxDifference=0-1;totalPixels=0-230">
|
|
<!-- The text after the end node must not be selected. -->
|
|
<span id="end">End Node <span id="start">Start Node</span></span> NOT SELECTED
|
|
<script>
|
|
let range = document.createRange();
|
|
range.setStart(start, 0);
|
|
range.setEnd(end, 2);
|
|
window.getSelection().addRange(range);
|
|
</script>
|