- From: Philip Rogers via GitHub <sysbot+gh@w3.org>
- Date: Tue, 09 Feb 2021 16:55:05 +0000
- To: public-svg-issues@w3.org
This recently came up in Chromium (see: https://crbug.com/1175868) and we noticed the [SVG2 spec](https://svgwg.org/svg2-draft/text.html#InterfaceSVGTextContentElement) still lists `tspan` and `textpath` as inheriting from SVGGraphicsElement which supports transforms. The class hierarchy in the SVG2 draft spec for `tspan` is: SVGTSpanElement -> SVGTextPositioningElement -> SVGTextContentElement -> SVGGraphicsElement. `textpath` is similar. Implementations seem to agree that `tspan` and `textpath` do not support transforms, whereas `text` does. Can the spec be updated to reflect this? One path would be to revert back to SVGTextContentElement inheriting from SVGElement instead of SVGGraphicsElement (see: [SVG11](https://www.w3.org/TR/SVG11/text.html#InterfaceSVGTextContentElement)), though this would require either duplication or multiple inheritance for SVGTextElement to support both SVGTextPositioningElement and SVGTextContentElement. -- GitHub Notification of comment by progers Please view or discuss this issue at https://github.com/w3c/svgwg/issues/210#issuecomment-776083440 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 9 February 2021 16:55:08 UTC