You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
context-stroke should be replaced by the stroke value where a marker is rendered. Since we render markers not as markers, but actual geometry we have to replace those special paints accordingly.
To Reproduce
<svgxmlns="http://www.w3.org/2000/svg"width="275"height="200"viewBox="0 0 275 200">
<defs>
<markerid="Triangle"viewBox="0 0 10 10"refX="1"refY="5"markerUnits="strokeWidth"markerWidth="4"markerHeight="3"orient="auto">
<pathd="M 0 0 L 10 5 L 0 10 z"fill="context-stroke"/>
</marker>
</defs>
<gfill="none"stroke-width="10">
<pathstroke="crimson"d="M 100,75 C 125,50 150,50 175,75 l 15 15"marker-end="url(#Triangle)"/>
<pathstroke="olivedrab"d="M 175,125 C 150,150 125,150 100,125"marker-end="url(#Triangle)"/>
</g>
</svg>
Expected behavior context-stroke should match the stroke color of the surrounding context. Similarly for context-fill.
Alternatively we could perhaps detect whether those values are used and simply retain the marker as marker instead of rendering it on our own. We'd lose the per-instance different sketching, but at least it still looks correct.
The text was updated successfully, but these errors were encountered:
Describe the bug
context-stroke should be replaced by the stroke value where a marker is rendered. Since we render markers not as markers, but actual geometry we have to replace those special paints accordingly.
To Reproduce
Expected behavior
context-stroke
should match the stroke color of the surrounding context. Similarly forcontext-fill
.Alternatively we could perhaps detect whether those values are used and simply retain the marker as marker instead of rendering it on our own. We'd lose the per-instance different sketching, but at least it still looks correct.
The text was updated successfully, but these errors were encountered: