![vaadin ui browser tab vaadin ui browser tab](https://guides.grails.org/vaadin-grails/img/charts-on-mobile-and-desktop.png)
![vaadin ui browser tab vaadin ui browser tab](https://dev.e-taxonomy.eu/redmine/attachments/download/1413/picture893-1.png)
![vaadin ui browser tab vaadin ui browser tab](https://static.vaadin.com/directory/user142257/icon/file8552985616892941692_1561444236951factory.png)
refresh the second tab /foo -> what should happen ?.navigate tab to /bar -> /foo no effect on first tab.tab open with route /foo and make changes.if the user opens the same page in another (same) browser window/tab, the old UI will be discarded.when the user refreshes the page, the same UI state is used as what was previously opened.I think we could probably add a way to be able to keep the active route target state in place if wanted. Google works: if you search for something, follow a link from there and then open again, then your previous search query will not be there any more, but it will be retained if you either navigate back or open the search result in a new browser tab that you just close to get back to the search result. In that way, the user could get back to their previous filtering state by using the back button in their browser, whereas the application's own navigation would lead to a clean state. users would show the unfiltered list of users whereas /users/foo would correspond to filtering the users by "foo". It's more about being able to preserve the state of one view while another view is active.Īnother way of thinking of the users filtering example is that the state can be captured in the URL. I don't think that example has anything to do with since the page is not reloaded when navigating between multiple views inside the same application.