has the following routes
app.vue > a.vue > b.vue
a.vue is a full-screen content
b.vue is also a full-screen content, and less parts are shared with a, so you can ignore
router-view at the bottom of a.vue
when a-> b, the content of an is above the page, but the content of b is below it
1. The judgment can be made in router.beforeEach.
Why not put 2.router-view in app.vue.
if you don't want to display it on the same page, you don't have to use nested routing.
< router-view > is placed in app.vue, and app.vue child routes a.vue, b.vue ~
give router-view a level of z-index
according to your description, an and b should be level, and router-view is more reasonable in app.vue.
if you have to app.vue > a.vue > b.vue, you can only use the style to set the content of b to absolute full screen.
when I first came into contact with vue, development, I found that this warning error will appear no matter where I click on the project page. I don t know if I have ever met anyone who made this error. Ask God for advice ...
for example, after the phone is bound, the status of the page should be updated. What is the specific method? ...
there is a background management system routing nesting relationship: app.vue > a.vue > b.vue I want to do this: send a request to verify the validity of token in app.vue send a data request in a b, and the parameters of the data request depend o...
vue has the following route nesting: > app.vue > a.vue > b.vue app.vue is the ingress, an is a level 2 route, and b is a child of a when accessing the b route, the request written in an and some column hook events will be called repeatedly. What ...