Note: the reason render_problem_v4.svg displayed correctly was because maskUnits was unset (defaulting to objectBoundingBox), while the other attached files had it set to userSpaceOnUse. Without setting appropriate x/y/width/height on the mask object, this can cause clipping as noted above.
File from #1 can be fixed by adding x="-558.528" y="-605.999" to the mask.
File from #4 can be fixed by adding x="-558.528" y="-605.999" to the mask.
File from #5 can be fixed by adding x="-334.42179" y="-615.72246" to the mask.
File from #8 can be fixed by adding y="952.36218" to the mask.
File from #9 can be fixed by adding x="-400" y="-30" to the mask.
These values all are the inverses of the transform applied to it's parent layer. Removing the maskUnits value is a simpler solution (that is robust against more complex transforms or multiple uses of the mask (but is not suitable when multiple objects try to share the same mask).
Hi,
We've moved our bug tracker to gitlab, so closing this issue and continuing to track this issue in https:/ /gitlab. com/inkscape/ inkscape/ -/issues/ 3183
Note: the reason render_ problem_ v4.svg displayed correctly was because maskUnits was unset (defaulting to objectBoundingBox), while the other attached files had it set to userSpaceOnUse. Without setting appropriate x/y/width/height on the mask object, this can cause clipping as noted above.
File from #1 can be fixed by adding x="-558.528" y="-605.999" to the mask.
File from #4 can be fixed by adding x="-558.528" y="-605.999" to the mask.
File from #5 can be fixed by adding x="-334.42179" y="-615.72246" to the mask.
File from #8 can be fixed by adding y="952.36218" to the mask.
File from #9 can be fixed by adding x="-400" y="-30" to the mask.
These values all are the inverses of the transform applied to it's parent layer. Removing the maskUnits value is a simpler solution (that is robust against more complex transforms or multiple uses of the mask (but is not suitable when multiple objects try to share the same mask).