Parallel views shouldn't affect each other's histories?


#1

When you have an abstract state with two child states, my understanding is the history from them shouldn’t interfere with each other?

I have an app that requires a tabbed interface that does not re-load tab content when you go between tabs (so ion-tabs is not suitable). I came up with a solution that simply uses ng-show and works great except for the fact that the histories of two child states seem to overlap when I don’t believe they should.

In the following codepen if you click on Tab2, then on Tab3, Tab3 will have a “back arrow” when it shouldn’t. They each have their own individual ion-nav-bar: