<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">onkeydown, onkeyup</td><td valign="top" nowrap class="compatibility">NN <span class="emphasis">4</span> IE <span class="emphasis">4</span> DOM <span class="emphasis">3</span>&nbsp;&nbsp;</td>
				</tr>
				<tr>
					<td valign="top" nowrap class="usage"><p class="literal"></p>
					</td><td valign="top" nowrap class="requirements">Bubbles: Yes; Cancelable: Yes&nbsp;&nbsp;</td>
				</tr>
				<tr>
					<td valign="top" colspan="2" class="description"><p>Fire when the user presses (<span class="literal">onkeydown</span>) and
releases (<span class="literal">onkeyup</span>) a keyboard key. These two
events fire on a focusable element or object for almost every key of
the keyboard, including function and navigation keys. The instance of
the <span class="literal">event</span> object for these events contains
information about the key (not the character) pressed. See Chapter 6 for details on cross-browser handling of
keyboard events. You cannot reliably inhibit critical <span class="emphasis">Ctrl</span> character sequences, but if you prevent
the default action of the <span class="literal">onkeypress</span> event for a
text form control, the character does not arrive at the text field.
</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>			All focusable rendered elements, plus <span class="literal">document</span> and
<span class="literal">window</span> objects.
</p>
					</td>
				</tr>
			</table>
		</div>
</body>
</html>