We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
Was this tool helpful to use?
Your feedback helps us make it better
An online reference guide for front-end developers to quickly look up JavaScript event names, categories, and browser compatibility.
No data
Overview
Understand what the tool solves, how it works, and the boundaries of its data.
This page is a fixed lookup table of JavaScript event-handler names, short descriptions, categories, and browser labels. Search for a familiar spelling such as onclick, onload, or onsubmit when reading older HTML or scripts. The rows mix everyday interactions with page, form, editing, and other historical entries, so treat the table as a vocabulary aid rather than a complete catalog of current web events.
The compatibility column uses labels such as IE and N for early Internet Explorer and Netscape versions. Those labels are historical annotations; they do not tell you whether a feature works in current Chrome, Firefox, Safari, or mobile browsers, and they do not show the target element or version range.
An inline handler or event-handler property often has an on prefix, as in onclick. The event type supplied to addEventListener is commonly written without that prefix: click, load, or submit. A match in this table helps identify a name, but it does not prove every historical name has a modern equivalent.
button.addEventListener("click", handler)button.onclick = handlerBoth forms connect code with an event, but addEventListener takes an event type and callback and can accept listener options. The event object passed to a listener carries details about the dispatched event, including its type and target.
Guide
Follow the workflow and verify inputs and outputs with practical examples.
Enter an event spelling or a word from its description. If an exact on* spelling is not found, try the likely type without the prefix, but do not infer support from the search result.
Use the column headings to sort the displayed records, and use the table controls to search across its text. Check the category and description together so similar names are not mistaken for the same behavior.
Move through the paginated results to inspect the full matching set. The table provides CSV and JSON export options; use an export when you need to compare or keep the listed reference rows.
For a common handler such as onsubmit, first identify the matching type, then check that the target supports it and register a listener on that target. For example, a form listener uses submit. Verify default actions, bubbling, and keyboard or touch access in the actual page rather than relying on a short table description.
Use cases
See how the tool fits into real work and everyday tasks.
When an inline on* attribute appears in a legacy page, use the index to decode the name and then check the current behavior before changing it.
Group entries by mouse, keyboard, form, and page activity, then test a current event in a small example to see its actual target and timing.
Use the table to catch spelling or terminology questions during review; use the current standard and browser documentation to make compatibility decisions.
Q&A
Find concise answers to common questions and confusing cases.
They are commonly two ways to refer to the same event: onclick is an event-handler property name, while click is the type string used with addEventListener.
No. They refer to historical browser generations and are not a current compatibility matrix. Check a current reference for the specific event, target, and browser versions you support.
This is a fixed, historical list rather than an exhaustive, maintained index of every current DOM event. Use a current platform reference to look up pointer, media, animation, or other newer event families.
Notes
Review scope, result limitations, and important precautions before use.
The table does not test a browser, track changing support, or provide version ranges and device differences. Some rows describe obsolete or browser-specific behavior. A row's presence is not proof that an event is standardized, available on a particular element, or appropriate for production code. Confirm current support and accessible input behavior before relying on an event.
Related
Discover related tools, collections, and available API capabilities.