You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to the spec, arc segments features flags: a fixed value 0 or 1. These flags are currently parsed as a number by svgo. This approach is more forgiving, but it's also a reason svg can be parsed incorrectly.
For example, an arc a1 1 0 001 1:
Rx
Ry
rot
large arc
sweep
x
y
Spec
1
1
0
0
0
1
1
svgo
1
1
0
001
1
As a result, svgs with comma-wsp? omitted after any of the flags makes svgo crash or produce incorrect results. This file is displayed correctly in all browsers and IE11+, but is broken after svgo 1.0.1.
According to the spec, arc segments features flags: a fixed value
0
or1
. These flags are currently parsed as a number by svgo. This approach is more forgiving, but it's also a reason svg can be parsed incorrectly.For example, an arc
a1 1 0 001 1
:1
1
0
0
0
1
1
1
1
0
001
1
As a result, svgs with
comma-wsp?
omitted after any of the flags makes svgo crash or produce incorrect results. This file is displayed correctly in all browsers and IE11+, but is broken after svgo 1.0.1.The text was updated successfully, but these errors were encountered: