mirror of
https://github.com/LadybirdBrowser/ladybird
synced 2026-05-03 13:02:09 +02:00
59a867d3e3
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.
18 lines
573 B
HTML
18 lines
573 B
HTML
<!DOCTYPE html>
|
|
<link rel="match" href="../expected/svg-stroke-paintstyle-with-opacity-ref.html" />
|
|
<meta name="fuzzy" content="maxDifference=0-1;totalPixels=0-2540">
|
|
<style>
|
|
body {
|
|
background-color: white;
|
|
}
|
|
</style>
|
|
<svg height="150" width="400">
|
|
<defs>
|
|
<linearGradient id="grad" x1="0" y1="0" x2="70%" y2="0">
|
|
<stop offset="0" stop-color="red"/>
|
|
<stop offset="1" stop-color="blue"/>
|
|
</linearGradient>
|
|
</defs>
|
|
<rect x="115" y="15" width="170" height="110" stroke="url(#grad)" stroke-opacity="0.3" stroke-width="10" fill="none" />
|
|
</svg>
|