[ http://issues.apache.org/jira/browse/TAPESTRY-52?page=all ]
Howard M. Lewis Ship resolved TAPESTRY-52:
------------------------------------------
Fix Version: 4.0
Resolution: Invalid
Assign To: Howard M. Lewis Ship (was: Tapestry Developer List)
This has been fixed in an earlier Tapestry 4.0 beta; you can now have
additional listeners on the server-side as new parameters of Form (cancel and
refresh), with corresponding client-side behavior to force a form to be
submitted in mode "cancel" or mode "refresh".
> Determining when user has refreshed a Tapestry web page
> -------------------------------------------------------
>
> Key: TAPESTRY-52
> URL: http://issues.apache.org/jira/browse/TAPESTRY-52
> Project: Tapestry
> Type: Bug
> Components: Framework
> Versions: unspecified
> Environment: Operating System: All
> Platform: All
> Reporter: Jeevan Bihari
> Assignee: Howard M. Lewis Ship
> Fix For: 4.0
>
> Currently there's no way for a Tapestry web page to find out whether a page
> is
> rendered due to a browser refresh or not. It would be great if Tapestry 3.1
> had
> this feature.
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
