Here is the case - for simplicity lets say my app consists from 5 pages (real situation is little more complex). Logically they are on one level. User may switch these 5 pages any way he wants and he can open any of these pages more than once. So lets say user opens pages in this order:

page1 -> page2 -> page4 -> page2 -> page4 -> page2

Every time I just push the new page in the Navigator, so the pages array becomes larger and larger even there are just 5 pages. The idea behind this is when user presses back button to go back logically in same order as pages were pushed, so show page2 and page4 two times again. The problem is all these pages stay in DOM too (I use React) and potentially DOM may become unnecessarily large. Is there are proper way to solve this issue? Maybe reset Navigator at some point to some reasonable amount of pages in the history? What about DOM?

Hello, is there a proper way to make Onsen 2.0 Navigator update location.hash? And vice-versa?

Great work about Onsen 2! As I see it is decoupled from Angular and in theory now it could work with any framework. My question is regarding React. Is there a tutorial, some sample, some additional info about using it with React? At least some best practices?

Also, some of the JS components still require Angular 1, like for example “ons-split-view” and “ons-sliding-menu”. Do you plan to fully decouple all the components from Angular in the final release, or there will be some Angular exclusive stuff?

Thanks!