lots of "unhandled" messages when using svgs from Sketch about flutter_svg HOT 7 CLOSED

That sounds good to me.

I think polygon should be supported tho, that seems like a bug.

from flutter_svg.

I guess <title> might just be a no-op, like <desc> appears to be?

from flutter_svg.

I think the polygon issue is when it is in a <defs> section:

    <defs>
        <polygon id="path-1" points="0 14 7.46666667 14 7.46666667 0 0 0"></polygon>
    </defs>

This gets referred to later:

                        <mask id="mask-2" fill="white">
                            <use xlink:href="#path-1"></use>
                        </mask>

from flutter_svg.

I've had some thoughts o ftrying to use <title> (but desc doesn't seem as useful) for a11y stuff, but nothing too concrete.

There's also been at least some discussion around supporting shapes in <defs>, but nothing concrete there yet either.

I would want to avoid adding too much overhead just to limit verbosity, but if all we're talking about is a simple hashset of elements I think that's probably ok. Of course, it'd be possible to preprocess SVGs to remove these kinds of elements too with XSLT or somesuch, which would add no overhead to the parser for it.

from flutter_svg.

I guess an "avoid verbose repeated output" switch could be on only in debug mode — a bit like the error reporting in flutter core that abbreviates repeated errors.

from flutter_svg.

I've checked in a fix for this in 000e17f - wrapped in an assert, so no impact on release code.

It will now track whether it's printed about a particular unhandled element and only print on the first time.

from flutter_svg.

awesome — I didn't think to use assert in this way. Thanks!

from flutter_svg.