You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If there is not registered directive named 'v-fake', Vue should ignore this attribute of an element.
What is actually happening?
Vue treat every 'v-[something]' attribute as directive, regardless if it is registered globally or locally, or not at all. It is trying to compute the value of 'v-' beginning attribute, and in effect throws TypeError, as it doesn't find property named like string passed to attribute.
if it is intentional, there should be information about such behavior in Vue docs. However in my opinion it should ignore such attributes.
The text was updated successfully, but these errors were encountered:
IMHO, I think the docs are clear enough. The v-* lookup has a good behavior. It makes debugging easier, if you want to add a property v-something and not want Vue to treat it as a directive, you should be using data attributes
So instead of <div v-fake/> it should be <div data-v-fake/>
Version
2.5.17
Reproduction link
http://jsfiddle.net/wf48v9de/3/
Steps to reproduce
Run the fiddle and look at console.
What is expected?
If there is not registered directive named 'v-fake', Vue should ignore this attribute of an element.
What is actually happening?
Vue treat every 'v-[something]' attribute as directive, regardless if it is registered globally or locally, or not at all. It is trying to compute the value of 'v-' beginning attribute, and in effect throws TypeError, as it doesn't find property named like string passed to attribute.
if it is intentional, there should be information about such behavior in Vue docs. However in my opinion it should ignore such attributes.
The text was updated successfully, but these errors were encountered: