jQuery Event Delegation: When .on() Should Take a Selector Argument
Binding click handlers to rows breaks as soon as new rows arrive. Here is how jQuery's .on() selector argument delegates events, plus where delegation costs you.
Loading…
ReadMeFeed / Community knowledge
#dom-events
Real questions. Useful conversations. Find the people who know your stack.
javascriptjQuery Delegated Events: One Listener That Survives Every Re-render
Delegated events with jQuery's .on(events, selector, handler) solve the classic dead-handler problem after dynamic re-renders. Here's how bubbling-based delegation works, a worked example, and when vanilla JS is the better call.
jQuery delegated event handling: how tightly should the container be scoped for a dynamic list
Delegated listener placement for dynamically added rows I am wiring click handling for a table whose rows are added and removed at runtime via AJAX, using jQuery 3.7. The documented approach is a single delegated listener, $(container).on('click', 'tr', handler) , so new rows work without re-binding. What I cannot settle is where container should live. Attac