On 2/8/07, Jan Vermeulen <[EMAIL PROTECTED]> wrote:
So is it a bad practice to simulate this back-button behaviour in buttons within the page ?
i think so, wicket handles all this for you by detecting changes to the page (when page.dirty() is called) We have a lot of pages where 'exit' or 'cancel' buttons
mean 'go back to the previous page'.
but what is a previous page? you said you only have a single page? wicket's ajax requests should never generate a new version, because ajax requests do not change the page url and thus there is no back-button history - and so a version is not needed. -igor
