-
-
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
Keep-Alive inside of transition not working with include #5346
Labels
Comments
To make use of the include option, you have to specify the |
Actually, forget that, it should work... |
posva
changed the title
Keep-Alive doesn't save the state of the slot component
Keep-Alive not working with include
Apr 1, 2017
In the meantime, you can use an exclude with the rest of components as a workaround |
posva
changed the title
Keep-Alive not working with include
Keep-Alive inside of transition not working with include
Apr 1, 2017
@posva Do you have any idea yet why the cache is being invalidated when I use include? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
2.2.6
Reproduction link
https://jsfiddle.net/50wL7mdz/24930/
Steps to reproduce
Click the "Switch view" button.
What is expected?
The "home" view's state should have been kept alive when switching to the other signin view.
What is actually happening?
Instead the "home" view is recreated everytime.
If I remove the include="home" option from keep-alive, it works as intended or if I remove the mode="out-in" option from the transition node, it also works as intended.
I've debugged this and it seems that when every time it switches the component, the "include" watch is somehow triggered with undefined as val parameter and then it's being triggered again with the correct "home" value but by then the first trigger has already removed the home node from the cache.
The text was updated successfully, but these errors were encountered: