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 2010/02/04 02:06:28 UTC
[jira] Updated: (TAP5-86) Extend Submit components to specify
behavior of submit: normal, reset or cancel
[ https://issues.apache.org/jira/browse/TAP5-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAP5-86:
-------------------------------------
Assignee: Howard M. Lewis Ship
Summary: Extend Submit components to specify behavior of submit: normal, reset or cancel (was: Submit add parameter type, with possible values submit,reset,cancel,cancelsubmit)
I think we can have the Form submit normally, bypassing validation, and recognize that on the server. Thus, no action link, etc.
I think we can make this work with the LinkSubmit component as well.
> Extend Submit components to specify behavior of submit: normal, reset or cancel
> -------------------------------------------------------------------------------
>
> Key: TAP5-86
> URL: https://issues.apache.org/jira/browse/TAP5-86
> Project: Tapestry 5
> Issue Type: New Feature
> Affects Versions: 5.0.15
> Reporter: Davor Hrg
> Assignee: Howard M. Lewis Ship
> Attachments: TAPESTRY-2109-R629196.patch, TAPESTRY-2109.patch
>
>
> There is a need for more submit types...
> although <input type="submit"> and <input type="reset"> are trivial even without a component,
> there is a problem when a type="cancel" is needed.
> The issue here is that in case of cancel client validation must be skipped, and that is not possible with current
> Submit component.
> I don't know how submit type=cancel works for T4 so I've implemented it how it seemed right for me.
> extract from javadoc for the "type" parameter
>
> * Determines the button behavior, <b>"submit"</b> - a normal form button, <b>"reset"</b> - reset form (locally),
> * "cancel" - works like an actionlink, generates a "cancel" event instead of "selected" and the form is not submitted
> * (if javascript is disabled form will be submitted, and "cancel" event fired as well),
> * <b>"submitcancel"</b> - works like "cancel" but behaves consistently with and without javascript
> * submission (this is usually desirable).
>
> input type=cancel uses javascript to redirect to an action link url, thus avoiding form submission,
> so I've added type=submitcancel which still submits the form but avoids client validation.
> both generate "cancel" event which is different from the "selected" event
> on top of all that the type=forced could be easily added to call "selected" event while skipping client side validation
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.