7e3f9e037da2aab40d0cc635312da60614126f31
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
SVG-edit, a web based SVG editor
Source code lives on GitHub: https://github.com/SVG-Edit/svgedit
Issue tracking and previewing remains on Google Code: https://code.google.com/p/svg-edit/
See AUTHORS file for authors.
SVG-edit contains code from these projects:
jQuery JavaScript Library v1.3.2 http://jquery.com/ Copyright (c) 2009 John Resig
jQuery js-Hotkeys http://code.google.com/p/js-hotkeys/ Copyright (c) 2008 Tzury Bar Yochay
jPicker http://www.digitalmagicpro.com/jPicker/ Copyright (c) 2009 Christopher T. Tillman
Description
Languages
JavaScript
96.4%
HTML
2.8%
CSS
0.7%
PHP
0.1%