-
-
Notifications
You must be signed in to change notification settings - Fork 33.7k
Weird v-bind attribute merging #11594
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
Comments
HTML attributes are not ordered. Besides, specific attributes take precedence over |
@posva In this case, Also, in code like this
v-bind does not take precedence not all, the produced |
I believe single attribute takes higher priority than the |
Yes, my bad, edited the comment |
@posva
Specific attribute does not take precedence over v-bind="{}", the result is |
Style and class have different behavior as the merge properties and dynamic ones have higher priority |
Version
2.6.11
Reproduction link
https://codepen.io/wenfang/pen/VwaeOxW?editors=1111
Steps to reproduce
None
What is expected?
Since
v-bind="{ foo: 'baz' }"
is written afterfoo="bar"
, I expected the final DOM div hasfoo="baz"
What is actually happening?
The DOM div has
foo="bar"
, is this intended?The text was updated successfully, but these errors were encountered: