[ http://issues.apache.org/jira/browse/BEEHIVE-231?page=history ]
Rich Feit updated BEEHIVE-231:
------------------------------
Fix Version: TBD
(was: V1)
I definitely think this needs to be addressed -- I just don't think we can do
it in the v1 timeframe. One possible options is to submit a token per-page
(perhaps optionally) -- this could be compared to what the server thinks is the
most recent page.
> Discuss Jpf.NavigateTo.currentPage expected behavior
> ----------------------------------------------------
>
> Key: BEEHIVE-231
> URL: http://issues.apache.org/jira/browse/BEEHIVE-231
> Project: Beehive
> Type: Task
> Components: NetUI
> Versions: V1Alpha, V1Beta
> Environment: This bug was discovered on Fedora Linux using Tomcat 5.0.25.
> Reporter: Jeremiah Johnson
> Assignee: Rich Feit
> Priority: Minor
> Fix For: TBD
> Attachments: BEEHIVE-231.tar
>
> It doesn't sound like the expected behavior has been defined for how
> Jpf.NavigateTo.currentPage should work in relation to back-button use, so I
> am entering this Jira task to ensure that the question gets addressed. If a
> user hits the back button (from page B, for example) to get to page A and
> then causes an action on that page (page A, again) to forward to
> Jpf.NavigateTo.currentPage, then the user will go to page B. When I ran
> across this case, I expected to see an updated page A rather than go to page
> B.
> I wish that I could say all of that more clearly, but I figure that it may be
> more helpful to attach a sample. I will attach a sample to clarify.
> - jeremiah
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
