New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Error: Param not a number: a,l" on SVG path #152
Comments
I don't know how you generated the path but it's kinda funky looking. The reason why it's failing is because the path has sections like this:
as opposed to
Note that when roughjs parses it, it thinks the number is I can change rough to interpret |
Thanks, the path is initially from wikipedia, but minified with svgo's convertPathData plugin. |
yes it must be because of the minification. |
I definetly can change the path, it's not an issue at all - I just though you might be interested in this kind of (pretty specific) behaviour. Maybe the path parser used by Firefox or Chrome could be found in their source code. |
This happend to me too while svg-icons conversion after upgraded from svgo 1.2.2 to the latest 1.3.2, though in browser icons work ok, but rough can not parse some paths. It also happens with I tried to "fix" paths and compare and changes but had no good luck with it. There is not only glued zeros ( Not even sure how to describe this issue in svgo repo. Besides. as I said there seems no issues with optimized icons in browser, only rough can't deal with them. UPD. There is an example. But this example seem to contain only glued zeros issue, other more complex icons had more complex changes that are not so easy to deal with from the first glance. And paths that are avaiabled in browser for this icon: v 1.2.2 (this works with rough)
v 1.3.2 (this error with rough)
|
There is another more complex example of converted with svgo paths 1.2.2 (this works with rough)
v 1.3.2 (this error with rough)
|
The path for which the error occurs is quite long. Here's a fiddle to replicate:
https://jsfiddle.net/87fjznso/1/
Error occurs in both
3.1.0
and current4.2.3
. I haven't tested other versions.The text was updated successfully, but these errors were encountered: