Thanks again Fran. I pinpointed the problem to props not being passed down. pageStack prop doesn’t seem to be going down from navigator to the page itself, it is always undefined on sub components. I was able to go around it using a computed property (deriving from a global pageStack) on each page but it’s less than ideal.

With regards to pageStack woe itself:
When I use this,

this.pageStack = [];
this.pageStack.push(page);

the back button keeps showing up even though clearly there is only 1 page in pageStack.

When I use this:

this.pageStack.length = 1;
this.pageStack[0] = page;

back button behaves as it should, i.e. not showing up.

Nevermind. Solved it using flexbox and overflow.

Is this correct ?

<ons-row>
   <ons-col>
      <ons-list>
   </ons-col>
   <ons-col>
      <ons-list>
   </ons-col>
</ons-row>

When scrolling, both lists scroll at the same time, regardless of which list the dragging starts on. I would expect the two lists to be independent when it comes to scrolling. What am I missing and how to achieve my goal?

Thank you Fran. I’m aware of the v-show directive. The problem as I see it is that at this stage anything below v-ons-navigator doesn’t seem to be reactive.
Pages get pushed into navigator’s pageStack and that part works fine. Altering pageStack through console yields the desired changes.
However if I try something like v-show=“showMe” and then alter showMe through console this does not change the DOM at all.

Are there maybe some caveats I need to be aware of when rendering multiple nested templates ?

Oh and I tried to both empty the pageStack before pushing new page and assigning a 1-page array and back button stays on at all times.

Thank you. Vanilla resetToPage doesn’t mix well with Vue, when supplied with the template, error comes up in the console. Considering the overwhelming circumstances and in the absence of a proper systemic solution I decided to do the unthinkable, in postPush event I simply set the back button to display:hidden. This only works if wrapped in setTimeout(fn,0) which makes me think that straight after calling postPush, Onsen sets the style of back button itself. At any rate, this needs looking at, really surprised there isn’t anything inbuilt for this - I would think - pretty common use case.

I’m using Onsen with Vue. When I try pageStack = [] followed by pageStack.push(somePage) this will result correctly in somePage being in pageStack. But the backButton is still being shown for some reason even if there’s no page to return to. How to deal with this ?

While I’ve looked through docs and resources, I haven’t quite managed to find an answer to this.
Does ONSEN UI contain some informational platform-specific classes? Like class “ios” when on running on iOS? Or is this problem solved only by using platform=“ios” in HTML?

I have found the automatic styling helpful but definitely in need of alteration.