ExecuteJS and CallbackResponse.AddJavaScriptToExecute

[RenSword]

Is there any difference between ExecuteJS() and CallbackResponse.AddJavaScriptToExecute()?

[Alexandre Machado]

ExecuteJS() calls AddJavaScriptToExecuteAsCDATA() internally *when* it is a callback response (async). If the code is being executed from a sync event, it will call AddToInitProc() which also executes the JS code, but when the page loads.

So, in general it is safe to replace CallbackResponse.AddJavaScriptToExecute() by ExecuteJS() (which is waaaay shorter) with the advantage that it will also work during a sync event.

[RenSword]

ExecuteJS() calls AddJavaScriptToExecuteAsCDATA() internally *when* it is a callback response (async). If the code is being executed from a sync event, it will call AddToInitProc() which also executes the JS code, but when the page loads.

So, in general it is safe to replace CallbackResponse.AddJavaScriptToExecute() by ExecuteJS() (which is waaaay shorter) with the advantage that it will also work during a sync event.

Okay, thanks alex