When someone interacts with a webpage, the browser sends events to the relevant JavaScript code. The scrollend event happens when scrolling completes with no pending position updates.
When scrollend happens
Scrolling completes with no pending position updates.
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
<div id="demo-target" style="height: 80px; overflow: auto; border: 1px solid">
<p>Top</p><p>More</p><p>More</p><p>More</p><p>Bottom</p>
</div>
<p id="event-status" role="status">Waiting for scrollend...</p>
<script>
const eventTarget = document.getElementById("demo-target");
const eventStatus = document.getElementById("event-status");
if (eventTarget) {
eventTarget.addEventListener("scrollend", (eventDetails) => {
eventStatus.textContent = "scrollend event received";
console.log(eventDetails.type, eventDetails.target);
});
}
</script>
Reading the code
The browser listens for scrollend 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.
Scroll and stop; browser support and timing can vary.
Try it in your browser
Open the page, show the Console panel, and follow this test: Scroll and stop; browser support and timing can vary. Then change one thing in the example and observe whether the event still fires.
Common Beginner Mistakes
- Expecting
scrollendto fire without its required user action or browser condition. - Scroll and stop; browser support and timing can vary.
- Adding repeated event listeners without considering cleanup or unwanted side effects.
Key Takeaways
scrollendreports scrolling completes with no pending position updates.addEventListener("scrollend", ...)listens for the event on the appropriate target.- Scroll and stop; browser support and timing can vary.