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

nested v-slot is not reactive when using abbreviated syntax (v-slot on component itself) combined with an v-if/v-else #10330

Open
dattn opened this issue Jul 31, 2019 · 1 comment · May be fixed by #10377

Comments

@dattn
Copy link

dattn commented Jul 31, 2019

Version

2.6.10

Reproduction link

https://codesandbox.io/s/vue-template-j1w3r

Steps to reproduce

In my example change the value by typing in the input field.
In the working example both values change.
In the not working example only the nested value changes.
The only difference is the wrapping <template> node

What is expected?

scoped slot params (controllerSlotData) should be reactive in both cases

What is actually happening?

scoped slot params (controllerSlotData) is not reative


The problem exists only when combining v-slot on component itself in combination with v-if/v-else

@dattn dattn changed the title nested v-slot is not reactive when using abbreviated syntax (v-slot on component itself) bombind with an v-if/v-else nested v-slot is not reactive when using abbreviated syntax (v-slot on component itself) combind with an v-if/v-else Jul 31, 2019
@dattn dattn changed the title nested v-slot is not reactive when using abbreviated syntax (v-slot on component itself) combind with an v-if/v-else nested v-slot is not reactive when using abbreviated syntax (v-slot on component itself) combined with an v-if/v-else Jul 31, 2019
zrh122 added a commit to zrh122/vue that referenced this issue Aug 10, 2019
@Quentin01
Copy link

I don't know why I didn't see this issue before opening #11553... Anyway, do you know when #10377 will be merged?

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

Successfully merging a pull request may close this issue.

3 participants