Add SVG clipping support for wipeouts and spatial filters#1112
Draft
chui-xelleron wants to merge 2 commits into
Draft
Add SVG clipping support for wipeouts and spatial filters#1112chui-xelleron wants to merge 2 commits into
chui-xelleron wants to merge 2 commits into
Conversation
chui-xelleron
marked this pull request as draft
June 9, 2026 22:54
chui-xelleron
force-pushed
the
fix/svg-clipping
branch
from
June 9, 2026 23:22
449e8b6 to
25c2b7c
Compare
chui-xelleron
force-pushed
the
fix/svg-clipping
branch
3 times, most recently
from
June 9, 2026 23:34
0125fea to
0b3caf6
Compare
chui-xelleron
force-pushed
the
fix/svg-clipping
branch
2 times, most recently
from
June 10, 2026 00:10
10e67da to
1240dc0
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds SVG output for wipeouts and spatial filter clips (with regression test).
This may be a breaking change for consumers that currently rely on wipeouts rendering as invisible, because the new output makes them visible as opaque white cover polygons.
For wipeouts, I was not sure whether the right SVG representation should be a true
clipPathor an opaque cover polygon. I implemented the opaque polygon approach for now because wipeouts behave like visibility masks in DWG, and SVG does not have a direct retroactive masking equivalent for already-rendered content.Is the opaque fallback acceptable here, or would you prefer a different SVG strategy for wipeouts?
Spatial filters still emit a clip path for clipped content, and when
DisplayBoundaryis enabled the boundary is drawn as a red outline as a visual aid.