01-12-2024, 11:22 PM
PerformAfterAsyncProcessing() is a JavaScript function of our own, it is called in the DoGenerateForm of our main base form (derived from TIWAppForm, and the parent for all our other intraweb forms.
If looks like the above JavaScript is now added before the formClass value itself is present.
'formClass' is a javascript variabele which is set in our $(document).ready( ) function, based on the value of IW_FormClass.
IWForm.pas sends the IW_FormClass to the browser (line 821) in procedure TIWForm.DoGenerateForm:
So my guess is that AddJavaScriptToExecuteAsCDATA may end up in the resulting page in a slightly different order using IW 15.5.x compared to IW 15.4.2 ??
Code:
procedure TIWCaiwBaseForm.DoGenerateForm(AStream: TIWRenderStream);
begin
inherited;
if WebApplication.IsCallBack then
WebApplication.CallBackResponse.AddJavaScriptToExecuteAsCDATA('PerformAfterAsyncProcessing();'#10);
end;If looks like the above JavaScript is now added before the formClass value itself is present.
'formClass' is a javascript variabele which is set in our $(document).ready( ) function, based on the value of IW_FormClass.
Code:
formClass = $("input[name=IW_FormClass]").val()IWForm.pas sends the IW_FormClass to the browser (line 821) in procedure TIWForm.DoGenerateForm:
Code:
Contents.AddHiddenField('IW_FormClass', Self.ClassName);So my guess is that AddJavaScriptToExecuteAsCDATA may end up in the resulting page in a slightly different order using IW 15.5.x compared to IW 15.4.2 ??

