Using link in view and enabling pushState at the same time will cause ‘page-not-found’ error, please check the sample below:
Child page won’t cover over the tabs of views as those tabs are not included in the same view as the child page is.
<div class="views tabs"> <div class="toolbar"> // views' tabs ... </div> <div class="view"> <div class="page">...</div> // child page </view> <div class="view">...</view> <div class="view">...</view> </div>
So based on current structure, I feel it is impossible to make child page to cover views’ tabs, but all the native app I see which contain double-tabbar are not based on this kind of structure.
This will cause route problem, because when pushState is enabled, after you open a child page in View1, you can switch to View2 while the route is still remain ‘…/#!/child-page/’. So, I’m really confused about in which scenario Views As Tabs can be used. Maybe, Views As Tabs was designed to solve the double-tabbar problem, but it can’t, or I don’t get the point to use it correctly.