tapestry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jochen Kemnade (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (TAP5-1427) Tapestry should track, on the client-side, changes to fields in a form, make it possible to determine if a form is "dirty" or not
Date Mon, 12 Jan 2015 08:10:57 GMT

     [ https://issues.apache.org/jira/browse/TAP5-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jochen Kemnade closed TAP5-1427.
--------------------------------
    Resolution: Invalid

We assume this is no longer relevant and therefore close it.
If you still have this issue in a recent Tapestry version (such as 5.3.8 or the latest 5.4
preview release), feel free to provide the necessary information and reopen.

> Tapestry should track, on the client-side, changes to fields in a form, make it possible
to determine if a form is "dirty" or not
> ---------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1427
>                 URL: https://issues.apache.org/jira/browse/TAP5-1427
>             Project: Tapestry 5
>          Issue Type: New Feature
>          Components: tapestry-core
>            Reporter: Howard M. Lewis Ship
>            Priority: Minor
>
> It's often nice to be able to add a confirmation message to submitting or canceling a
form; it would be better if there was a way to know if the form itself has any "dirty" changes
to be committed or lost.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message