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
Singult doesn't recognize svg <animate> element #22
Comments
Nope, you're using it exactly right and even found where you'd need to put the fix. |
Okay, thanks! As this is probably not limited to
I don't like 1, but it seems the simplest. I like 2 a lot, but I'm not sure if it's possible. I like 3 as well. If What do you think? I'd be happy to work on this problem when I have time. |
What about just filling out |
I didn't know namespaced tags are supported, how could I not try, I'll use them for now:)
Well, they're namespaced for a reason, I guess, which is to avoid overlapping. There're some elements which are same in svg and html, e.g. |
Hello,
I may be doing something wrong, but I don't understand what.
I use c2 (and consequently singult) to create an
<svg>
element, which contains a<path>
with<animate>
in it.<path>
is displayed just fine, however the newly-created<animate>
element is not recognised by Chrome as an SVGElement and (consequently?) the animation doesn't happen at all.I found out that if add the
animate
intore_svg_tags
, like that:it works really well.
Do you think it's a singult's issue, or I'm mis-using it somehow?
Thank you!
The text was updated successfully, but these errors were encountered: