This is probably more appropriate for the tacos list (unless it got
buried?), but I don't see any reason why it couldn't be pushed until after
the scripts are processed, since that's technically the "end" of the client
request cycle.
A bug report will ensure it gets done.
On 3/4/06, Jeremy <[EMAIL PROTECTED]> wrote:
>
> Hi. Seems like the tacos framework should call
> updateObject.responseComplete
> after processing the scripts embedded in the incoming <ajax-response>
> element. That way, the incoming fragment can actually redefine the
> responseComplete method of the update object. Any reason not to change
> this?
>
>
>
>
> FYI. Here's some pseudocode for what's happening during a
> defaultLinkAction
> call:
>
> defaultLinkAction(){
> loadDojoResponse() {
> processScripts("preprocess" and "jsincludes" element nodes);
> processAjaxResponse() {
> for each response node {
> updateObject.beforeAjaxUpdate();
> loadElement() {
> weave the new nodes into the DOM
> updateObject.ajaxUpdate();
> }
> }
> processScripts("postprocess" element nodes);
> updateObject.responseComplete();
> }
> }
> processScripts("ajax-response" element nodes);
> }
>
>
> --
> No virus found in this outgoing message.
> Checked by AVG Free Edition.
> Version: 7.1.375 / Virus Database: 268.1.2/274 - Release Date: 3/3/2006
>
>
>
