Hi there,
we are currently working on a webapp where we use the single page logic (hide/show) in order to navigate from a table view to a detail view of an entity.
We ran into the issue now, that if someone tries to use the back buttons in the browser and not from the webapp, one gets redirected to another page, so not as intended from the detailview back to the table view.
Is there a way to keep the single page logic while still being able to use the browser buttons for back-navigation?
weweb already creates a single page application. this means that instead of showing/hiding sections you can actually build different pages and the navigation between them will not reload the page but will switch the content of the page taking care of browser navigation.
if you want to keep using the show/hide workaround you can use code to intercept when the browser is about to go back in history and change the behaviour. this way is very easy to break the native functionality and have frustrated users.