Re: [svgwg] getPathSegAtLength had consistent implementation behavior for invalid paths from CSS Meeting Bot via GitHub on 2018-07-02 (public-svg-issues@w3.org from July 2018)

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Mon, 02 Jul 2018 18:48:03 +0000
To: public-svg-issues@w3.org
Message-ID: <issue_comment.created-401898548-1530557282-sysbot+gh@w3.org>

The Working Group just discussed `getPathSegAtLength`.

<details><summary>The full IRC log of that discussion</summary>
&lt;ericwilligers> Topic: getPathSegAtLength<br>
&lt;ericwilligers> GitHub: https://github.com/w3c/svgwg/issues/313<br>
&lt;ericwilligers> I have removed the milestone<br>
&lt;AmeliaBR> Eric: This has been removed from SVG 2, although it's still technically an open issue on the SVG Paths spec, if that ever gets worked on.<br>
&lt;AmeliaBR> https://github.com/w3c/svgwg/issues?q=is%3Aopen+is%3Aissue+label%3AAgenda%2B<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/svgwg/issues/313#issuecomment-401898548 using your GitHub account

Received on Monday, 2 July 2018 18:48:07 UTC