Sorry I don’t have a codepen for this, because it involves displaying the url history as well.
I have a navbar in a page like this:
<f7-navbar title="Enter Code" backLink="Back" backLinkUrl="/landing" :backLinkForce="true" />
The last route in the history is a different url (call it
/home). When I click on the back link, it does render the landing page, but in the url it shows
/home. Then when I click on a link button on the
landing page, it flashes the destination page, then immediately navigates to the
I stepped through the debugger after clicking on the back link, and saw that in back.js, it does indeed mutate router.history and view.history to replace
landing. But then it calls
History.back(), which (in history.js) calls
window.history.back(). It’s that call that changes the url to
/home. So it looks like f7 has its own history list, and
window.history have its native stack. How are they in sync? Something seems off here. Am I misunderstanding?