Comments and changes to this ticket
Technically this is due to the way d="..." and points="..." is parsed. The way it's done now means polygons won't work in Chrome, but paths do (for the most part). The fix will likely involve changing the operator/coordinate parsing in both places:
- strip any delimiters if they exist (comma),
- for sensible parsing, put a space after the MLHVCSQT operators,
- split entire d/points string on \s+, then run through the thusly built token list, case-switching on letters.
- State changed from blocked to peer-review-requested
(from [8bc30e74327d1c3ab385275429fa320a7b485d09]) fixed parsePoly() [#800 state:peer-review-requested] http://github.com/annasob/processing-js/commit/8bc30e74327d1c3ab385...
- State changed from super-review-requested to staged
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »