You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2011/01/26 22:58:46 UTC

[jira] Created: (TAP5-1427) Tapestry should track changes to fields in a form, make it possible to determine if a form is "dirty" or not

Tapestry should track 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (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

Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TAP5-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship updated TAP5-1427:
---------------------------------------

    Summary: 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  (was: Tapestry should track changes to fields in a form, make it possible to determine if a form is "dirty" or not)

> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (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

Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TAP5-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship updated TAP5-1427:
---------------------------------------

    Summary: 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  (was: Tapestry should track changes to fields in a form, make it possible to determine if a form is "dirty" or not)

> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.