Open wfwalker opened 8 years ago
there will be a new API https://svgwg.org/specs/paths/#InterfaceSVGPathData
and a polyfill for that https://github.com/jarek-foksa/path-data-polyfill.js
as well as a polyfill for the old API https://github.com/progers/pathseg
Also see the official chromium bug https://code.google.com/p/chromium/issues/detail?id=539385
https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/EDC3cBg9mCU
The SVGPathSeg interface [1][2] was used to individually manipulate a path’s components. One use case was to modify any given component (e.g., a cubic arc command in the center of a path) without explicitly re-creating the path from a string.
[1] http://www.w3.org/TR/SVG11/single-page.html#paths-InterfaceSVGPathSeg [2] http://www.w3.org/TR/SVG11/paths.html#InterfaceSVGPathElement
Motivation
This interface was difficult to use and has been removed from the SVG spec in favor of a new, awesomer API in the Paths module (https://lists.w3.org/Archives/Public/www-svg/2015Jun/0044.html).