<html>
<link rel="stylesheet" href="josh.css">
<body bgcolor="#FFFFFF">

		<div id="Description">
			<table cellpadding="0" cellspacing="0" border="0" width="100%" class="main">
				<tr><td valign="top" class="name">onunload</td><td valign="top" nowrap class="compatibility">NN <span class="emphasis">2</span> IE <span class="emphasis">3</span> DOM <span class="emphasis">2</span>&nbsp;&nbsp;</td>
				</tr>
				<tr>
					<td valign="top" nowrap class="usage"><p class="literal"></p>
					</td><td valign="top" nowrap class="requirements">Bubbles: No; Cancelable: No&nbsp;&nbsp;</td>
				</tr>
				<tr>
					<td valign="top" colspan="2" class="description"><p>Fires just before the current document begins to unload due to
impending navigation to a new page, form submission, or window
closure. This event fires after the <span class="literal">onbeforeunload</span>
event in browsers that support that event. In most browsers, the
actual document unloading does not wait for the
<span class="literal">onunload</span> event handler function to complete.
Therefore, if the function performs too many actions, especially
those that rely on script variables and elements in the current page,
those references may become invalid while the function runs, creating
script errors (of the "undefined"
or "object not found" variety).
Therefore, keep <span class="literal">onunload</span> processing to a minimum.
</p>
							</td>
				</tr>
				<tr>
					<td valign="top" colspan="2" class="CLEARSEPARATION">&nbsp;</td>
				</tr>
				<tr>
					<td valign="top" colspan="2" class="typicaltargets"><span class="title">Typical Targets</span></td>
				</tr>
				<tr>
					<td colspan="2"><p>			The <span class="literal">body</span> and <span class="literal">frameset</span> elements,
plus the <span class="literal">window</span> object.
</p>
					</td>
				</tr>
			</table>
		</div>
</body>
</html>