-
-
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
cascade v-slot don't emit change of variables from scope #9438
cascade v-slot don't emit change of variables from scope #9438
Comments
I'm not sure if the current spec allows putting the default slot inside Edit: it works just removing |
I'm curious to know if spec allows, in fact I can't remove the slot name from my |
It seems to be a bug. Uncomment the fifth line (adding a default slot) and it works: https://jsfiddle.net/leopiccionia/bjr340vo/ |
Correct ! :) |
Version
2.6.2
Reproduction link
https://jsfiddle.net/cn09xg4k/
Steps to reproduce
There is a
card
component withuserName
andlastName
. Each 200ms these variables are updated.Between
user
andcard
components there is a wrapper, just to use a slot.What is expected?
Variables in
user
component should be refreshedWhat is actually happening?
These two variables are displayed only once and never updated
The text was updated successfully, but these errors were encountered: