- From: Chris Lilley via GitHub <sysbot+gh@w3.org>
- Date: Mon, 07 Jan 2019 18:10:40 +0000
- To: public-svg-issues@w3.org
@BigBadaboom said: > Is it maybe time to assign this to the too-hard basket, and go with @r12a's option 1 and 2? That is, deprecate the multi-value attributes, and instead recommend that authors use <tspan> for the situations when the code point algorithm fails? @litherum said: > I wish I was around when this feature was being introduced, so I could have argued that authors should do their own counting by putting each character inside its own <text>. I wish we could deprecate this feature. Apart from `tspan` vs. `text` (and `tspan` is preferable so you can select across the element boundary) these seem similar to me. Deprecate the under-specified lists of dx and dy, and define them to use UTF-16 byte pairs for counting. Tell authors to use explicit markup when they want something different. Leave some future spec to add any additional counting methods and text segmentation strategies and so on (tests from @r12a show there is little interop here, for the non-trivial cases). I do want to see this resolved, but I don't see a resolution (plus associated browser updates) inside a couple of months. -- GitHub Notification of comment by svgeesus Please view or discuss this issue at https://github.com/w3c/svgwg/issues/537#issuecomment-452027607 using your GitHub account
Received on Monday, 7 January 2019 18:10:41 UTC