You haven't said what mechanisms you're using to navigate between pages. But my guess is that to achieve the behavior you want you'll need to eliminate the middle page and put its code into the first page, with the Run button on the first page causing a form submission followed by a redirect to the last page. This leaves you with a standard Post-Redirect-Get pattern, which ensures the back button will be safe. Then you're only challenge is to add some kind of progress indicator to the form submission action on the first page, perhaps with JavaScript. On Jan 31, 2013 1:55 AM, "harishpatarla" <harishpata...@gmail.com> wrote:
> Hi, > > I am working on a web app and in this we add test xml scripts to run them. > I have a page ViewTest.tml(test/view) and this page has Run button to > trigger the execution which then navigates to next page > (/execution/run/progress).After it is done we navigate to next page > ShowResults. > > Now if the user wanted to see the test script he has executed and uses back > button to navigate to ViewTest page it redirects first to > /execution/run/progress and the same test script gets executed again.Now I > could go back and see the test script. > > What i want to avoid here is when the user clicks back button and navigates > to /execution/run/progress it should not execute the test script. > > I do not want to disable the back button but stop the operation that is > being done when a user uses back button and navigates to that page > > > > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/Disable-operations-caused-due-to-back-and-forward-buttons-tp5719689.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
