Skip to content
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

<a> tag is wrongly assumed to be in html namespace instead of svg #6506

Closed
roblabla opened this issue Sep 4, 2017 · 3 comments · Fixed by #6511
Closed

<a> tag is wrongly assumed to be in html namespace instead of svg #6506

roblabla opened this issue Sep 4, 2017 · 3 comments · Fixed by #6511

Comments

@roblabla
Copy link

roblabla commented Sep 4, 2017

Version

2.4.2

Reproduction link

https://jsfiddle.net/4s3hj82k/

Steps to reproduce

  1. Create a template using as the root element

  2. Try to use it in an

What is expected?

I either expected vue to understand that the is supposed to be an SVG a tag (and not an xhtml a tag), or a way for me to override vue's decision and give it the proper namespace (e.g. making svg:a work ?)

What is actually happening?

Vue is creating the tag as an xhtml:a tag, and so the browser doesn't render it.

You can make it render by wrapping it in an . This is undesirable however, for many reasons. Having a way to explicitly tell vue the namespace from which to create the element would be nice.


SVG <a> tag : https://developer.mozilla.org/fr/docs/Web/SVG/Element/a

@roblabla roblabla changed the title a tag is wrongly assumed to be in html namespace instead of svg <a> tag is wrongly assumed to be in html namespace instead of svg Sep 4, 2017
@yyx990803
Copy link
Member

Please provide an actual reproduction.

@roblabla
Copy link
Author

roblabla commented Sep 4, 2017

Woops, looks like I messed up the link copy pasting ? Anyway, trying to put one back up together.

@roblabla
Copy link
Author

roblabla commented Sep 4, 2017

Here's the repro : https://jsfiddle.net/4s3hj82k/

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

Successfully merging a pull request may close this issue.

2 participants