Review repeated event listeners and consolidate them on a shared parent element. This approach, called event delegation, handles dynamically added items and reduces individual listeners while preserving the intended interaction behavior.
Use when reviewing scripts, client components, bundles, or runtime behavior related to Use event delegation for dynamic content. Inspect both source code and the browser execution path so fixes target the real bottleneck or bug.
Run score Not tested
See how to installevent-delegation finds identical event handlers attached to individual list items or table rows and helps move them to a shared parent element. This technique, called event delegation, uses events bubbling from children to their parent to handle elements added later. It also covers identifying the intended element with event.target.closest() and checking interactions in the browser.
Use it when items added through AJAX or user actions do not respond to clicks. It also helps when many list items or table rows have the same listener and you want to review memory use or processing overhead. The skill examines both source code and browser execution paths to narrow down what needs changing.
closest() and when to use target.”This approach relies on events bubbling to a parent. Check that the intended target is identified correctly, and remove the parent listener when removing the container. After changes, test browser interactions, including elements added dynamically.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI checked the SKILL.md for operations that need care and for setup requirements. The score comes only from actually running the skill (hands-on test).
Not counted in the score. Rated by AI (OpenAI Codex) as of Oct 23, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
Adding hundreds of individual event listeners for list items or table rows consumes significant memory and creates performance overhead. Dynamic content (items loaded via AJAX or rendered after user actions) won't have event listeners unless you re-attach them after each update — event delegation solves both problems at once.
Find any code in this file that attaches the same event handler to multiple elements in a loop. Suggest event delegation as an alternative.
Refactor these per-element event listeners to use event delegation on the common parent container.
Explain event delegation, how event bubbling enables it, and when to use closest() vs target.
Review scripts, client components, and browser execution paths related to Use event delegation for dynamic content. Flag exact imports, event handlers, runtime side effects, or blocking operations that violate the rule, and state how the change should be verified in the browser.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/javascript/event-delegation
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Create and review custom 404 pages that help visitors recover from broken or moved links through search and navigation. Check the rendered page and HTTP response so missing content returns a proper 404 status.
Audit or create a dedicated About page that explains a website’s purpose and identifies its people or organization. Review the rendered output and supporting information, including expertise and contact details, to find gaps.
Review and add automated accessibility checks for components, pages, and continuous integration workflows. Use axe-based tools to detect structural and attribute issues, while identifying checks that still need keyboard or screen reader testing.
Review sign-in, registration, multi-factor authentication, and account recovery for accessibility barriers. Find blocked paste, difficult code entry, and inaccessible backup methods, then suggest authentication paths that support password managers, autofill, or device approval.
Review form errors, success messages, and live updates so screen reader users receive important notifications. Check the HTML delivered to the browser, announcement settings, display duration, and dismissal controls, then identify specific elements that need changes.
Review HTML tables so screen reader users can understand how headers and data relate. Check header markup, table descriptions, and merged cells, then identify specific fixes and ways to verify them.