-
-
Notifications
You must be signed in to change notification settings - Fork 33.7k
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
v-once within component template makes all component instances static #6826
Labels
Comments
Dafrok
added a commit
to Dafrok/vue
that referenced
this issue
Oct 17, 2017
jkzing
added a commit
to jkzing/vue
that referenced
this issue
Oct 18, 2017
jkzing
added a commit
to jkzing/vue
that referenced
this issue
Oct 18, 2017
13 tasks
yyx990803
pushed a commit
that referenced
this issue
Oct 18, 2017
close via #6837 |
@yyx990803 hi, do you know when a new release that includes this fix will be released approximately? thanks for the awesome project :) |
erweixin
pushed a commit
to erweixin/vue
that referenced
this issue
Dec 15, 2017
…js#6837) * test(once): failing test for vuejs#6826 * fix(core): static trees should be cached on options (vuejs#6826)
f2009
pushed a commit
to f2009/vue
that referenced
this issue
Jan 25, 2019
…js#6837) * test(once): failing test for vuejs#6826 * fix(core): static trees should be cached on options (vuejs#6826)
aJean
pushed a commit
to aJean/vue
that referenced
this issue
Aug 19, 2020
…js#6837) * test(once): failing test for vuejs#6826 * fix(core): static trees should be cached on options (vuejs#6826)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
2.5.2
Reproduction link
https://jsfiddle.net/8L92f8Lm/
Steps to reproduce
v-once
within its template and renders dynamic contentWhat is expected?
Each instance of the component renders its associated content
What is actually happening?
All instances of the component render the same content
This seems to be a regression from 2.4.4 as witnessed by https://jsfiddle.net/8L92f8Lm/1/.
The text was updated successfully, but these errors were encountered: