[ https://issues.apache.org/jira/browse/WICKET-4286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13205148#comment-13205148 ]
Dan Retzlaff commented on WICKET-4286: -------------------------------------- I agree there isn't a good solution without AJAX history, but I respectfully disagree that 1.4 worked the same. In 1.4 reloading the page returned the most recent version of a page (the one with the most AJAX updates); in 1.5 those AJAX changes can be lost on reload/back. > ListView causes page ID increment > --------------------------------- > > Key: WICKET-4286 > URL: https://issues.apache.org/jira/browse/WICKET-4286 > Project: Wicket > Issue Type: Bug > Components: wicket > Affects Versions: 1.5.3 > Environment: any > Reporter: Mark Lichtenberg > Assignee: Igor Vaynberg > Attachments: ajaxtest1.5.3.tar.gz > > > A ListView with setReuseItems(false) causes the page ID to increment when the > page is reloaded or the back button is pressed. This new ID is not reflected > in the URL so Ajax actions against the new ID are lost when navigating away > and back again. > Steps to reproduce in quickstart > 1) Load quickstart project in browser > 2) Click "Link to Other" then click browser's back button. > 3) Notice the log statement indicates the HomePage ID is 2, yet the URL > remains at ID 0 > 4) Click "Ajax Increment Link" a few times > 5) Click "Link to Other" then click browser's back button > 6) Notice the counter is at zero, and subsequent clicks to the "Ajax > Increment Link" start from zero. The current page ID output in the log is 4. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira