- From: Paul LeBeau via GitHub <sysbot+gh@w3.org>
- Date: Fri, 31 Mar 2017 05:33:34 +0000
- To: public-svg-issues@w3.org
BigBadaboom has just created a new issue for https://github.com/w3c/svgwg: == Remove SVGGeomertyElement interface from <mesh>? == https://svgwg.org/svg2-draft/single-page.html#shapes-InterfaceSVGMeshElement `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. Please view or discuss this issue at https://github.com/w3c/svgwg/issues/310 using your GitHub account
Received on Friday, 31 March 2017 05:33:42 UTC