I updated the JIRA (https://issues.apache.org/jira/browse/WICKET-5290) to note potential uses cases as follows:
1. **Page parameters** (usually for stateless pages). Most probably very common use case, why make a page stateful just to save a few variables? Just define a few page params and let LoadableDetachableModel load the rest. Instead of storing the page in the session, store the page state in the URL and let history API manage that "state". 2. **BreadCrumb(Panel) components**. Navigable components, but still inside a single page 3. **Inter-page navigation**. Page navigation but only target several components. Perhaps via whitelisting or blacklisting or a combination of both. This seems most challenging compared to the two cases above. Hendy -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Wicket7-History-API-support-for-navigable-AJAX-pages-components-tp4660502p4661444.html Sent from the Forum for Wicket Core developers mailing list archive at Nabble.com.
