7e3f9e037d
The SVGPathSeg API is being removed from the spec [1] and is being removed in Chromium 47 [2]. I implemented a drop-in polyfill[3] so svg-edit users are not broken as browsers migrate away from the path seg api. This patch simply imports the upstream pathseg.js and updates all dependencies. With this change all tests pass in Chrome 46 (with the path seg api), Chrome 47 (without the path seg api), and there are no changes to tests in Safari 9.01 or Firefox 43. I also manually tested svg-edit while developing the polyfill and could not find any broken features. [1] https://lists.w3.org/Archives/Public/www-svg/2015Jun/0044.html [2] https://groups.google.com/a/chromium.org/d/msg/blink-dev/EDC3cBg9mCU/OvElJgOWCgAJ [3] https://github.com/progers/pathseg |
||
---|---|---|
.. | ||
qunit | ||
all_tests.html | ||
contextmenu_test.html | ||
coords_test.html | ||
draw_test.html | ||
history_test.html | ||
jquery-svg_test.html | ||
math_test.html | ||
path_test.html | ||
recalculate_test.html | ||
sanitize_test.html | ||
select_test.html | ||
svgtransformlist_test.html | ||
svgutils_test.html | ||
test1.html | ||
units_test.html |