cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Wallez (JIRA)" <>
Subject [jira] Commented: (COCOON-1774) Fine Tuning Ajax Handling in CForms
Date Fri, 10 Feb 2006 22:44:37 GMT
    [ ] 

Sylvain Wallez commented on COCOON-1774:

Can you elaborate on the need for widget-level ajax="false"?

Also the submit handlers cannot be kept after an Ajax submit, as some of the handlers can
be registered by widgets that are replaced by the Ajax response

> Fine Tuning Ajax Handling in CForms
> -----------------------------------
>          Key: COCOON-1774
>          URL:
>      Project: Cocoon
>         Type: Improvement
>   Components: Blocks: Forms, Blocks: Ajax
>     Versions: 2.1.8
>     Reporter: Eric Meyer
>     Assignee: Antonio Gallardo
>  Attachments: fi-styling-ajax-false.patch.txt
> Currently, it's all or nothing when it comes to using AJAX on a form. With this enhancement,
form widgets can be marked with  <fi:styling ajax='false' />, and they will trigger
a non-ajax form submission.
> This was particularly useful on the main submit buttons on a form inconjunction with
the fi:validation-messages element (see for
why fi:validation-messages doesn't work with AJAX). Regardless, I believe it is useful to
give the developer control over which widgets use AJAX and which do not.
> Note that the patch files also include a fix to a separate AJAX issue. 
> forms_onsubmitHandlers = null
> Causes problems when in AJAX mode - submit handlers are only called the first time an
ajax submit is called. Thereafter, the array of handlers is null, and none are called. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message