FAQ: Why doesn''t the JavaScript OnLoad event work in the body tag? (Legacy Web Controls)

Legacy Controls NOTICE

This article references our legacy Web Forms Web Viewing controls (WebImageViewer, WebAnnotationViewer, WebThumbnailViewer). It is preserved for archival purposes, but support strongly recommends using our modern HTML5 web controls: WebDocumentViewer, WebDocumentThumbnailer instead)

INFO: WebDocumentViewer Whitepaper - Getting Started With Web Viewing

Main Article Content

NOTE: This article applies to versions 2.x and above.

The WebImageViewer uses the Body's OnLoad event to initialize the client side components of the control. This is necessary because as the page loads, elements can move depending on how long images or objects take to load, and whether or not the size attributes of those objects are defined.

You can use atalaInitClientScript to run code in the OnLoad event. This function queues up each string sent to it and tries to execute it as JavaScript code. This allows you to execute multiple scripts OnLoad. This function is located in ClientTools.js, and is required by the WebImageViewer control when using RichClient, FullClient, and client side printing.

Here is an example that will pop up an alert when the page is finished loading:

	<script language="javascript" type="text/javascript"> 
	var mycode = 'alert("test");'; 
	atalaInitClientScript(mycode); 
	</script>

Original Article:

Q10089 - INFO: Why doesn''t the JavaScript OnLoad event work in the body tag?