- From: Fredrik Söderqvist via GitHub <sysbot+gh@w3.org>
- Date: Fri, 28 Jul 2017 18:50:09 +0000
- To: public-svg-issues@w3.org
Seems like a reasonable tiebreaker strategy, feel free to file a Chromium/Blink bug and I'll see if I can get to it eventually. (Bugs for other engines would probably be good from an interoperability standpoint too.) And to follow the tangent (sorry, couldn't resist!) from https://github.com/w3c/svgwg/issues/333#issuecomment-318720395 about `getSlopeAtLength()`. If that's intended as a companion to `SVGGeometryElement.getPointAtLength()`, I don't think that would be much work to implement. (Slightly more efficient would be to add a method to return both the point and slope/angle/normal - or even one taking an array of lengths and return an array of [point, slope] tuples, or else we'll probably need to make sure there's a lookup cache to prevent N^2 behavior...) -- GitHub Notification of comment by fsoder Please view or discuss this issue at https://github.com/w3c/svgwg/issues/333#issuecomment-318734051 using your GitHub account
Received on Friday, 28 July 2017 18:50:09 UTC