I just forgot to said, the below comment does not address concretely
COCOON-1774. I think closing COCOON-1774 was a right decision. It is
more about the process and not due this bug. I saw first: COCOON-1714,
and I think it should not be closed until fixed.
Best Regards,
Antonio Gallardo.
Antonio Gallardo escribió:
Jean-Baptiste Quenot (JIRA) escribió:
[ http://issues.apache.org/jira/browse/COCOON-1774?page=all ]
Jean-Baptiste Quenot closed COCOON-1774.
----------------------------------------
Resolution: Won't Fix
Please reopen the issue if the problem persists with the new Dojo
stuff. Thanks!
I don't think it is the best way to close bugs. IMHO, the first part
of a problem resolution is the problem identification and an open
issue without a patch provides this first part. I would left open this
bug (and onther of the current closed) until somebody comes with a
solution. I don't know if you talked about this in GT2006, but if jira
now becomes only a patch repository, I will like to know. At least we
should vote for this policy change. Please don't take it personally. ;-)
WDYT?
Best Regards,
Antonio Gallardo.
Fine Tuning Ajax Handling in CForms
-----------------------------------
Key: COCOON-1774
URL: http://issues.apache.org/jira/browse/COCOON-1774
Project: Cocoon
Issue Type: Improvement
Components: Blocks: Forms, Blocks: Ajax
Affects Versions: 2.1.8
Reporter: Eric Meyer
Assigned To: 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
http://issues.apache.org/jira/browse/COCOON-1570 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.
