[
https://issues.apache.org/jira/browse/TAP5-1884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13235084#comment-13235084
]
Howard M. Lewis Ship commented on TAP5-1884:
--------------------------------------------
Having some trouble with this patch. I think it should probably be converted
into a parameter whose default is driven by the symbol.
In addition, once a Form is deactivated (for submit), it is not clear how it
can be reactivated. This is relevant in some Ajax/Zone scenarios where the Form
may update some other Zone on the page. That's a good reason to allow it to be
configured on a Form-by-Form basis using a parameter ... or provide some
additional API to re-enable a Form as part of the partial page update (i.e.,
define a Tapestry.Initializer for this purpose).
> Provide native support to suppress multiple (redundant) form submissions
> ------------------------------------------------------------------------
>
> Key: TAP5-1884
> URL: https://issues.apache.org/jira/browse/TAP5-1884
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-core
> Affects Versions: 5.3, 5.4
> Reporter: Howard M. Lewis Ship
> Attachments: Archive.zip
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
