P粉9305342802023-08-24 14:21:35
jQuery.fn.on
has a good explanation in the documentation一个>.
in short:
So, in the example below, #dataTable tbody tr
must exist before generating code.
$("#dataTable tbody tr").on("click", function(event){ console.log($(this).text()); });
If new HTML is injected into the page, it is best to attach event handlers using delegated events, as described below.
The advantage of delegated events is that they can handle events from descendant elements that are later added to the document. For example, if the table exists but rows are added dynamically using code, the following will handle it:
$("#dataTable tbody").on("click", "tr", function(event){ console.log($(this).text()); });In addition to being able to handle events on descendant elements that have not yet been created, another advantage of delegated events is that they may reduce overhead when many elements must be monitored. On a data table with 1,000 rows in
tbody, the first code example attaches handlers to 1,000 elements.
tbody, and the event only needs to bubble up one level (from the clicked
tr to
tbody).
Note: Delegated events do not work with SVG.
P粉5471709722023-08-24 11:57:21
Starting with jQuery 1.7, you should use jQuery.fn.on
with the selector parameter populated:
$(staticAncestors).on(eventName, dynamicChild, function() {});
illustrate:
This is called event delegation and it works as follows. This event is attached to the static parent (staticAncestors
) of the element that should be handled. This jQuery handler is fired every time an event is fired on this element or one of its descendant elements. The handler then checks if the element that triggered the event matches your selector (dynamicChild
). When there is a match, your custom handler function is executed.
Until then, the recommended method is to use live()< /代码>
:
$(selector).live( eventName, function(){} );
However, live()
was deprecated in 1.7, replaced by on()
, and removed entirely in 1.9. live()
Signature:
$(selector).live( eventName, function(){} );
...can be replaced with the following on()
signature:
$(document).on( eventName, selector, function(){} );
For example, if your page dynamically creates an element with the class name dosomething
, you can bind that event to an already existing parent (which is the core of the event ) The problem here is that you need something existing to bind to, rather than binding to dynamic content) this can be (and the easiest option) is document
. But keep in mind that document
may not be the most efficient option.
$(document).on('mouseover mouseout', '.dosomething', function(){ // what you want to happen when mouseover and mouseout // occurs on elements that match '.dosomething' });
Any parent that exists when the event is bound will do. For example
$('.buttons').on('click', 'button', function(){ // do something here });
Applies to
<div class="buttons"> <!-- <button>s that are generated dynamically and added here --> </div>