You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org> on 2008/06/20 23:27:45 UTC
[jira] Closed: (TAPESTRY-2459) Submit components fires its event
after "validateform" event, should be before (this is a change from prior
releases)
[ https://issues.apache.org/jira/browse/TAPESTRY-2459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAPESTRY-2459.
------------------------------------------
Resolution: Fixed
Fix Version/s: 5.0.14
> Submit components fires its event after "validateform" event, should be before (this is a change from prior releases)
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-2459
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2459
> Project: Tapestry
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.0.13
> Environment: Every
> Reporter: Massimo Lusetti
> Assignee: Howard M. Lewis Ship
> Priority: Critical
> Fix For: 5.0.14
>
>
> The order (timing) of the selected event fired by the Submit
> components has changed.
> It fires after the validateform event.
> The old behavior was the opposite as stated in the documentation of
> the component.
> This seems caused by TAPESTRY-2311.
> For replicating the error simply put a submit component inside a form
> which has both the onValidateForm and onSuccess event handler methods
> and you'll see the onSelected event handler method called after the
> onValidateForm but before the onSuccess.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org