-
-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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 deeply nested router-views display the last visited component component #2923
Closed
lxcuso4 opened this issue
Sep 8, 2019
· 2 comments
· Fixed by #2930, WFCD/warframe-hub#411, mariazevedo88/hash-generator-js#38, tghelere/valorize-vidas#9 or tghelere/DeliVuery#36
Closed
keep-alive deeply nested router-views display the last visited component component #2923
lxcuso4 opened this issue
Sep 8, 2019
· 2 comments
· Fixed by #2930, WFCD/warframe-hub#411, mariazevedo88/hash-generator-js#38, tghelere/valorize-vidas#9 or tghelere/DeliVuery#36
Labels
Comments
Similar to #2552 if anybody wants to try fixing this |
posva
changed the title
Router resove can't work
keep-alive deeply nested router-views display the last visited component component
Sep 9, 2019
zrh122
added a commit
to zrh122/vue-router
that referenced
this issue
Sep 17, 2019
you are right |
posva
pushed a commit
to zrh122/vue-router
that referenced
this issue
Jan 14, 2020
posva
added a commit
that referenced
this issue
Jan 14, 2020
* fix(router-view): fix deeply nested keep-alive router-views displaying Fix #2923 * chore: upgrade chromedriver * refactor(view): add keepAlive check Co-authored-by: Eduardo San Martin Morote <posva@users.noreply.github.com>
This was referenced Mar 1, 2020
This was referenced Mar 19, 2020
This was referenced Mar 28, 2020
This was referenced Apr 6, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
3.1.3
Reproduction link
https://jsfiddle.net/lxcuso4/cu6keqw2/28
Steps to reproduce
Click on childA
Click on index
Click on childB
What is expected?
we want to show B page
What is actually happening?
but actually A page dispaly
This behavior happens when we use keep-alive and have three layers of nested routing
The text was updated successfully, but these errors were encountered: