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
SVGMeshElement is currently defined as supporting the SVGGeometryElement interface. However it is not obvious how most of the methods of SVGGeometryElement would apply to a mesh.
What is the equivalent path of a mesh? The concatenation of all the stop paths? That doesn't seem useful.
The only method of this interface that might be useful is isPointInFill(). But the rest of the members of the interface (pathLength, isPointInStroke, getTotalLength(), getPointAtLength()) do not make sense for a mesh.
If it were to keep SVGGeometryElement, then I think we need to define the behaviour of these other functions. Otherwise I think SVGMeshElement should be switched to SVGGraphicsElement instead.
The text was updated successfully, but these errors were encountered:
BigBadaboom
changed the title
Remove SVGGeomertyElement interface from <mesh>?
Remove SVGGeometryElement interface from <mesh>?
Mar 31, 2017
All the other methods can be derived once you have the path. A <mesh> is a shape element that defines both its fill and its path from the referenced <meshgradient>.
No problem. It was a topic we discussed a lot last year, and the spec did change a few times. Trying to create sensible interface inheritance was the main reason we split meshes into two elements, one for the paint server (meshgradient) and one for the actual shape (mesh).
https://svgwg.org/svg2-draft/single-page.html#shapes-InterfaceSVGMeshElement
SVGMeshElement
is currently defined as supporting theSVGGeometryElement
interface. However it is not obvious how most of the methods of SVGGeometryElement would apply to a mesh.What is the equivalent path of a mesh? The concatenation of all the stop paths? That doesn't seem useful.
The only method of this interface that might be useful is
isPointInFill()
. But the rest of the members of the interface (pathLength
,isPointInStroke
,getTotalLength()
,getPointAtLength()
) do not make sense for a mesh.If it were to keep SVGGeometryElement, then I think we need to define the behaviour of these other functions. Otherwise I think
SVGMeshElement
should be switched toSVGGraphicsElement
instead.The text was updated successfully, but these errors were encountered: