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

Why was "Vue.config.prefix" removed? #2415

Closed
paceband opened this issue Feb 29, 2016 · 3 comments
Closed

Why was "Vue.config.prefix" removed? #2415

paceband opened this issue Feb 29, 2016 · 3 comments

Comments

@paceband
Copy link

Hi,
Is there a reason why was "Vue.config.prefix" removed? Performance issues?
In order to have our html W3C compliant, we could set it like this:
Vue.config.prefix = "data-v";
Or do you have a nice way to make it work?
Maybe using a jQuery selector that would change all "data-v-" by "v-" in the init event?
Any ideas?
Thanks

@sirlancelot
Copy link

You could probably do so during the "beforeCompile" event, which is fired just before the element goes through Vue's compilation.

@yyx990803
Copy link
Member

Vue directives are removed in the rendered markup, so your eventual markup will be W3C compliant.

@MachinisteWeb
Copy link

MachinisteWeb commented Jul 19, 2016

This tips for « v- » is not anymore relevant « #221 » for Windows phone and what yyx990803 said here « #273 (comment) » is not relevant anymore too...

So, how I could use « data-v-* » instruction to keep « source » from server W3C Compliant in order to pass this tests for example : https://validator.w3.org/ ?

EDIT : I just thinking if this « v-bind:class » syntax become « data-v-bind:class » that will not change the validation failure so... maybe « osef ».

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

No branches or pull requests

4 participants