When someone interacts with a webpage, the browser sends events to the relevant JavaScript code. The keyup event happens when a pressed key is released.
When keyup happens
A pressed key is released.
You can listen for it using addEventListener(). That keeps event handling separate from HTML attributes such as onclick and works well with modern code organization.
A small working example
<label for="demo-target">Try the input</label>
<input id="demo-target" name="sample" type="text" required>
<p id="event-status" role="status">Waiting for keyup...</p>
<script>
const eventTarget = document.getElementById("demo-target");
const eventStatus = document.getElementById("event-status");
if (eventTarget) {
eventTarget.addEventListener("keyup", (eventDetails) => {
eventStatus.textContent = "keyup event received";
console.log(eventDetails.type, eventDetails.target);
});
}
</script>
Reading the code
The browser listens for keyup on the relevant target. When the event occurs, the callback receives eventDetails, updates the status message and logs the event name and target in Developer Tools.
Release a key after keydown.
eventDetails.key identifies the released key; use keyboard interactions only where they improve native controls.
The form example is for learning. HTML constraint validation is helpful feedback, but the server must still validate submitted values and handle requests safely.
Try it in your browser
Open the page, show the Console panel, and follow this test: Release a key after keydown. Then change one thing in the example and observe whether the event still fires.
Common Beginner Mistakes
- Expecting
keyupto fire without its required user action or browser condition. - Release a key after keydown.
- Adding repeated event listeners without considering cleanup or unwanted side effects.
Key Takeaways
keyupreports a pressed key is released.addEventListener("keyup", ...)listens for the event on the appropriate target.- Release a key after keydown.