[
https://issues.apache.org/jira/browse/TRINIDAD-1515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12737571#action_12737571 ]
Dave commented on TRINIDAD-1515:
--------------------------------
This back button issue and PPR issue (
https://issues.apache.org/jira/browse/TRINIDAD-1544) prevents us from using Trinidad. We use JSF RI, Tomahawk and Richfaces, our app works well. But we want to take advantage of Trinidad mobile support.
We use t:saveState to keep backing bean data in request scope, so we do not need to manage data in session scope. For our application we have not found a way to manage data efficiently in session scope to support Back button. We hope we could use Trinidad after these two issues are solved.
> Browser back button does not work
> ----------------------------------
>
> Key: TRINIDAD-1515
> URL:
https://issues.apache.org/jira/browse/TRINIDAD-1515> Project: MyFaces Trinidad
> Issue Type: Wish
> Components: Components
> Affects Versions: 1.2.12-core
> Environment: Trinidad 1.2.11, jsf ri 1.2.12, tomahawk 1.2.12, IE7
> Reporter: Dave
> Priority: Minor
>
> When we use jsf ri and tomahawk, our jsf app works well for browser back button. But after we use Trinidad, browser back button does not work. Consider the following senario:
>
> 1. show a table of employees (backing bean data is a list of employees)
> 2. click an employee A and show the employee,(backing bean data is now changed to the employee)
> 3. click browser back button
> 4. click an employee B. Employee B will not be shown because the backing data has been changed to employee A in stop 2.
>
> The same page is used and <t:saveState> is used to keep backing bean data.
> I looked the generated HTML viewState values in the steps above. They are the same. That means that only the same view(stored view tree in server side) is used. For jsf/tomahawk, I believe different view trees are used for the senario above and thus back button works.
>
> Back button is often used by users.
> Trinidad should add an option: save different view state for each request or each differeant page.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
