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

SVG <a> tags don't work #2178

Closed
zocky opened this Issue May 24, 2014 · 5 comments

Comments

Projects
None yet
4 participants
@zocky

zocky commented May 24, 2014

<a xlink:href=".."> tags inside <svg> don't get recognized and created as SVG tags, they're created as HTML tags instead.

Simply adding them to the list of known SVG tags in package htmljs "fixes" this, but not correctly, because it causes all HTML <a> tags to be created as SVG tags.

@n1mmy n1mmy added the Blaze label Jun 10, 2014

@estark37

This comment has been minimized.

Contributor

estark37 commented Jun 20, 2014

Hi @zocky. What's the problem that this is causing for you?

It's easy enough to fix but I'd like to be able to write a test case. When I create an SVG element with <a xlink:href=".."> inside it, the link works fine even though it's created as an HTML element.

@estark37

This comment has been minimized.

Contributor

estark37 commented Jun 20, 2014

This is the (hacky) fix, by the way: e6fb17e

This bug is also related to #1977, where tags are getting created as SVG elements when they should be created as HTML elements.

@estark37

This comment has been minimized.

Contributor

estark37 commented Jun 23, 2014

Never mind, I was doing something silly -- now I see that the tag doesn't work inside an SVG when it's created with document.createElement. Fix with a test coming soon!

@estark37

This comment has been minimized.

Contributor

estark37 commented Jul 9, 2014

Thanks again @zocky; this is fixed on devel now.

@fvpDev

This comment has been minimized.

fvpDev commented Apr 1, 2016

I just ran into this problem myself; So how do I update meteor to devel version?
I'm using v1.3 right now.

Lol nvm about dev version...I just realized how old this issue was. What shall I do?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment