You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Dave (JIRA)" <de...@myfaces.apache.org> on 2009/06/21 05:20:07 UTC
[jira] Created: (TRINIDAD-1515) Browser back button does not work
Browser back button does not work
----------------------------------
Key: TRINIDAD-1515
URL: https://issues.apache.org/jira/browse/TRINIDAD-1515
Project: MyFaces Trinidad
Issue Type: Bug
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
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.
[jira] Resolved: (TRINIDAD-1515) Browser back button does not work
Posted by "Andrew Robinson (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/TRINIDAD-1515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Robinson resolved TRINIDAD-1515.
---------------------------------------
Resolution: Invalid
Please see email response on the users mailing list
> Browser back button does not work
> ----------------------------------
>
> Key: TRINIDAD-1515
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1515
> Project: MyFaces Trinidad
> Issue Type: Bug
> 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
>
> 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.
[jira] Commented: (TRINIDAD-1515) Browser back button does not work
Posted by "Dave (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/TRINIDAD-1515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12724045#action_12724045 ]
Dave commented on TRINIDAD-1515:
--------------------------------
The special case can be solved as described in the email. But it is a workaround, not a general programming model. It is hard to deal with all senarios, if users press Back Button several times. That requires developers to keep all the backing bean data and manage them carefully in session scope. In jsf ri/tomahawk, they save views for each request, so developers do not have to worry about what to keep in order for Back button to work.
IF trinidad can let developers to make a choice on when to save tree view states, it would solve the problem automatically.
Choices are:
1. the way that Trinidad works currently
2. save tree view for each request as JSF ri/Tomahawk works
In our case, we will choose the 2nd because our application is data driven, i.e. what data on server decides what to show to users. Could you please reopen this case and add option 2.
> Browser back button does not work
> ----------------------------------
>
> Key: TRINIDAD-1515
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1515
> Project: MyFaces Trinidad
> Issue Type: Bug
> 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
>
> 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.
[jira] Reopened: (TRINIDAD-1515) Browser back button does not work
Posted by "Andrew Robinson (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/TRINIDAD-1515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Robinson reopened TRINIDAD-1515:
---------------------------------------
> 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.
[jira] Commented: (TRINIDAD-1515) Browser back button does not work
Posted by "Dave (JIRA)" <de...@myfaces.apache.org>.
[ 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.