- From: Sebastian Zartner via GitHub <sysbot+gh@w3.org>
- Date: Fri, 12 Jul 2019 20:50:05 +0000
- To: public-svg-issues@w3.org
> There's nothing to remove (yet). The entry in the text chapter describes how the CSS property (set with CSS) would apply to SVG text. Oh, yeah, I missed that. So then it's missing from the [properties index](https://svgwg.org/svg2-draft/propidx.html). 😉 > Of course, if no browser has implemented that, either, we may need to mark it as risk. I've now tested the example given in the spec. in all three mentioned browsers and unfortunately they also do not support the property. So I've filed a [request for implementation in Gecko](https://bugzilla.mozilla.org/show_bug.cgi?id=1565675). For Chromium/Blink there was [already one filed](https://bugs.chromium.org/p/chromium/issues/detail?id=366550). If you test it in Safari and it also doesn't work there, I can also file an enhancement request in WebKit's bug tracker. > But that will get bundled with changes to defer all SVG multi-line text functions to a future version of the spec. Even though `text-overflow` would be useful even without the other new properties, e.g., for text on a path. Off-topic for this issue, but is there some central place where all the ideas for a future SVG spec. and the features removed from SVG 2 are collected and discussed? > Re MDN: Yes, remove it from the attributes section. It would be helpful to have information in the regular CSS `text-overflow` page, that it is defined to be valid on SVG, but support is poor. I removed the page again. As no tested browser currently supports the property and annotation 36 indicates that it's value seems to be controversial and therefore may be removed from the spec., I decided now not to document it for now and rather wait for whether it get's traction. Sebastian -- GitHub Notification of comment by SebastianZ Please view or discuss this issue at https://github.com/w3c/svgwg/issues/711#issuecomment-511028910 using your GitHub account
Received on Friday, 12 July 2019 20:50:07 UTC