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
If a shape's "fill" property is an url(), then attr->hasFill gets set to 2, but then at this point NanoSVG when checking for hasFill 2 checks to see if there's a gradient and if there's no gradient it just sets the shape fill type to NSVG_PAINT_NONE. This is causing my app to misbehave because it handles PAINT_NONE in a particular way and even if it can't currently access the fill url() through nanoSVG currently, it's important to know it is filled.
I could create a PR, but I don't know if this is how you want it done upstream because nanosvgrast won't know how to deal with the new NSVG_PAINT_SPECIAL type.
The text was updated successfully, but these errors were encountered:
If a shape's "fill" property is an url(), then attr->hasFill gets set to 2, but then at this point NanoSVG when checking for hasFill 2 checks to see if there's a gradient and if there's no gradient it just sets the shape fill type to NSVG_PAINT_NONE. This is causing my app to misbehave because it handles PAINT_NONE in a particular way and even if it can't currently access the fill url() through nanoSVG currently, it's important to know it is filled.
I have locally patched this with:
I could create a PR, but I don't know if this is how you want it done upstream because nanosvgrast won't know how to deal with the new NSVG_PAINT_SPECIAL type.
The text was updated successfully, but these errors were encountered: