- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Tue, 13 Nov 2018 22:39:00 +0000
- To: public-svg-issues@w3.org
Ah, cool, that's exactly it. (And, as it turns out, *nobody* follows that: Chrome starts up the rendering right where it would have rendered the next character on the path, rather than at the end of the path; Firefox starts up the rendering at an *x* position where it would have rendered the next character in the path, and at a *y* position where it would have been without any `textPath` at all.) ------ Okay, so we have an answer. `textPath` definitely should have been a top-level rendering element rather than a `text` child, but it still has a clear definition of how it should render in concert with `text`. The only missing piece would be how it renders with a `tspan` parent; I submit that the two logical possibilities are: 1. It ignores the `tspan` parent, and continues to just render on the path 2. It renders the same as if the `tspan` were moved into the `textPath` element instead. I'm not sure if either one is more obviously "correct" than the other. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/svgwg/issues/580#issuecomment-438465722 using your GitHub account
Received on Tuesday, 13 November 2018 22:39:02 UTC