mattsteve
commented
4 years ago Since they just made the fix so you can add a custom event to handle tab buttons (not yet published to npm), you can do this manually, assuming named views still work with ion-vue-router.
Vue Router Named Views: https://router.vuejs.org/guide/essentials/named-views.html
<template>
<ion-tabs>
<ion-vue-router v-show="selectedTab === 'tab1'" name="tab1router" />
<ion-vue-router v-show="selectedTab === 'tab2'" name="tab2router" />
<ion-tab-bar slot="bottom">
<ion-tab-button
:selected="selectedTab === 'tab1'"
@click="selectedTab = 'tab1"
>
Tab 1
</ion-tab-button>
<ion-tab-button
:selected="selectedTab === 'tab2'"
@click="selectedTab = 'tab2"
>
Tab 2
</ion-tab-button>
</ion-tab-bar>
</ion-tabs>
</template>
<script>
export default {
data() {
return {
selectedTab: 'tab1'
}
}
};
</script>Router config
const router = new VueRouter({
routes: [
{
path: '/',
components: {
default: Foo,
tab1router: Tab1Component,
tab2router: Tab2Component
}
}
]
})
lights0123
michaeltintiuc
aileksandar
I'm writing a mobile app. Each tab should have its own navigation stack, i.e. you can navigate in the "News" tab, switch to the about tab and hit "About", and switch back to the News tab, leaving off right where you were, in both scroll position and path. In my app, I'm using version 1.1.2 of
@modus/ionic-vue, as it does not require a router for tabs. The way I have this working is that each tab has its ownVueRouterrunning inabstractmode. This shouldn't be possible in other navigation modes, as going back should not change tabs. Other apps, such as the ionic-vue-conference-app, try to implement this, but fail badly. Other than being broken by using relative paths, switching between tabs doesn't retain the previous navigated path. This is a key feature in many apps, and is holding me back to this old version. See this demo of what I currently have, which is what I want. What is the proper way to do this?