Why is my jquery .on('change') not working for dynamically added selects

Event binding to elements that are not in the DOM on initial page load will not work. You need to bind to an element further up the DOM that exists to allow the event to trickle down. This is usually the approach that I take:

$(document).on({ change: function() { alert('helo'); } }, '#x select'); $(document).on({ change: function() { alert('helo'); } }, '#y select'); 

I prefer it as you can add subsequent events easily.

$(document).on({ change: function() { alert('helo'); }, blur: function() { alert('helo'); } }, '#x select'); 

Don't use .live()/.bind()/.delegate(), though. You should use .on().

for both static and dynamic select changes

$(document).on('change', 'select', function (e) { // do something }); 

Your event binding is set on $(document).ready(). However, if you are dynamically adding them later (like via jQuery.appendTo() or the like), the newly added components need to be binded since they were not part of the inital one that happened in $(document).ready(), which only runs once when the page is loaded and the DOM is initially done.

Correct syntax:

 $('#x').on( 'change', 'select', function () { alert('helo'); } ); 

So syntax of on() for dynamic element seems:

$(staticParent).on( eventName, target, handler); 

The whole point of .on() is so that you can bind the event to something other than the document. This is what the now depreciated .live() did and it is inefficient in most cases. You are ment to bind the event to the closest parent element that will not be dynamically changed.

As far as I am aware this is the correct syntax:

$('#x').on('change', 'select', function(){ alert('hello'); }); 

If #x or #y will be changed, wrap them on an element and bind the event to that.

This is easy. Whatever class or id your targeting, try being more precise but no need to include a super parent.

Example of wrong way:

 $('#tablecontent').on('change', '#tablecontent > table.CampaignGrid > tbody > tr > td', function(e) { console.log('IN TABLE CONTENT CHANGE'); var value = e.target.value; $('button#updateLuck').prop('disabled', false).css({'color': '#000', 'font-weight': 600}); //alert($(ele[0]).html()); });

CORRECT WAY:

 $('#tablecontent').on('change', 'table.CampaignGrid > tbody > tr > td', function(e) { console.log('IN TABLE CONTENT CHANGE'); var value = e.target.value; $('button#updateLuck').prop('disabled', false).css({'color': '#000', 'font-weight': 600}); //alert($(ele[0]).html()); });

Notice I dropped the super parent: '#tablecontent'

It all about clarity.

• V

The word in square brackets is the alt text, which gets displayed if the browser can't show the image. Be sure to include meaningful alt text for screen-reading software.

Came across this as I could not get my dynamically created selects which came back from an ajax post with dynamic id's, to trigger the event.

$(document).on('change', 'select', function (e) { $("#theDiv select").on("change",function(){ post("SelectChanged");} ); }); 

This would not work until I had changed something first so I added

$("#theDiv select").on("change",function(){ post("SelectChanged");} ); 

However this not meant, that after the change, all other changes then fired twice. This may not be very good practice. But what I did was to to put in a function that is called at the start and each return of ajax.

 `function myFuncs(){ $('#theDiv select').unbind('change'); $('#theDiv select').on('change' function(){ post('selectChanged'); }); }` 

But had to unbind at start of each function call else it doubled up the functions each time. I am sure there must be a proper way to do this, I just haven't found it yet. Thanks for starting the question.