7 Commits (7cf976cfb8a518812e0a7692af65ac2103b1d487)

Author	SHA1	Message	Date
Brett Zamir	dc6ab72480	- Update Opera and jQuery links ... - Use `https://` (fix #172), including in prompt for URL and relevant code comments (where available and naturally not on namespaces) - Comment out broken link in svg-editor.html - Trailing space	2018-05-18 13:48:47 +08:00
codedread	4043c6e537	Change all tab indentations to 2sp indentation. Addresses issue #37	2018-05-17 21:02:30 -07:00
Brett Zamir	a3b3525789	- Linting (ESLint): Finish ... - Fix: Globals (x, y) in `mouseMove` - Fix: Global (element, d_attr->dAttr) in `mouseDown` - Fix: Avoid `drawnPath` not defined error - Docs: sp.	2018-05-17 11:34:21 +08:00
Brett Zamir	340915be4e	- Linting (ESLint): Finish extensions and most files in editor/; unfinished: `editor/svg-editor.js`, `editor/svgcanvas.js` ... - Linting (ESLint): Fix ignore file paths - History `elem` fix	2018-05-16 12:08:41 +08:00
Philip Rogers	f5f9e627d7	Update pathseg.js to fix Firefox 59+ path editing ... Firefox 59 removed some SVG path seg APIs which breaks path editing. This change updates pathseg.js to the latest version which contains a fix for Firefox 59. I checked that Firefox 58 (pre-api-change), Firefox 59 (post-api-change), Chrome 65, and Safari Tech Preview can all edit paths correctly with this change. This change has a lot of diffs due to minor changes in pathseg.js since the first time it was imported into svgedit. This fixes issue #216	2018-02-26 18:10:26 -08:00
Philip Rogers	c5dadfbe77	Include upstream fix for shape editing: 11f7e5a958	2015-11-06 21:08:23 -08:00
Philip Rogers	7e3f9e037d	Add pathseg.js, a polyfill for the SVGPathSeg API ... 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	2015-11-04 19:25:30 -08:00