You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2014/03/28 22:40:17 UTC
[jira] [Commented] (TAP5-2310) Add ability to store component
actions that are only executed when the form is cancelled
[ https://issues.apache.org/jira/browse/TAP5-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13951440#comment-13951440 ]
ASF subversion and git services commented on TAP5-2310:
-------------------------------------------------------
Commit e8ca15f1b61dbaadfc597c1e543b1adf922f880f in tapestry-5's branch refs/heads/master from [~hlship]
[ https://git-wip-us.apache.org/repos/asf?p=tapestry-5.git;h=e8ca15f ]
TAP5-2310: Support form actions only triggered if the form is cancelled
> Add ability to store component actions that are only executed when the form is cancelled
> ----------------------------------------------------------------------------------------
>
> Key: TAP5-2310
> URL: https://issues.apache.org/jira/browse/TAP5-2310
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-core
> Affects Versions: 5.4
> Reporter: Howard M. Lewis Ship
> Labels: forms
> Fix For: 5.4
>
>
> In some circumstances, it is necessary to do some work to cleanup a component that is inside a Form, when the Form is cancelled. The "cancelled" event is insufficient, since the event propagates up, but the component in question may be a sibling of the Form, or even a child of a sibling.
--
This message was sent by Atlassian JIRA
(v6.2#6252)