mirror of
https://github.com/LadybirdBrowser/ladybird
synced 2026-04-27 10:07:15 +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.
24 lines
577 B
HTML
24 lines
577 B
HTML
<!DOCTYPE html>
|
|
<link rel="match" href="../expected/svg-clip-path-and-mask-ref.html" />
|
|
<meta name="fuzzy" content="maxDifference=0-1;totalPixels=0-12">
|
|
<style>
|
|
body {
|
|
background-color: white;
|
|
}
|
|
</style>
|
|
<svg height="200" viewBox="0 0 100 100">
|
|
<mask id="mask">
|
|
<circle cx="60" cy="35" r="35" fill="white"/>
|
|
</mask>
|
|
|
|
<clipPath id="clip">
|
|
<circle cx="40" cy="35" r="35" />
|
|
</clipPath>
|
|
|
|
<path
|
|
id="heart"
|
|
d="M10,30 A20,20,0,0,1,50,30 A20,20,0,0,1,90,30 Q90,60,50,90 Q10,60,10,30 Z" />
|
|
|
|
<use clip-path="url(#clip)" mask="url(#mask)" href="#heart" fill="red" />
|
|
</svg>
|