- From: Cameron McCormack via GitHub <sysbot+gh@w3.org>
- Date: Sat, 10 Nov 2018 06:42:51 +0000
- To: public-css-archive@w3.org
> For your first example, this is identical to `<rect style="display:contents"><rect /></rect>`; we don't consider it reasonable to render the inner `rect` there, so we shouldn't render the inner `textPath` here. That seems reasonable to me. > For your second, I wasn't aware that `tspan` caused `textPath` to not render. That's an odd and unfortunate detail. The fact that you can put `tspan` _inside of_ `textPath` validly, but not outside, seems weird. `<textPath>` really should have been a top level element, rather than being required to be a child of a `<text>`. That you can't wrap a `<textPath>` with a `<tspan>` is probably because it doesn't make sense to apply the `<tspan>`'s positioning attributes to the `<textPath>`, but then again you can have positioning attributes on the `<text>` too. Oh well. -- GitHub Notification of comment by heycam Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3302#issuecomment-437562865 using your GitHub account
Received on Saturday, 10 November 2018 06:42:53 UTC