You can trigger a custom event on the newly added DOM element that can be picked-up by a jQuery event handler: //bind to our custom event for the `.sub-element` elements $(‘#container’).on(‘custom-update’, ‘.sub-element’, function(){ $(this).html(‘<b>yaay!</b>’); }); //append a new element to the container, //then select it, based on the knowledge that it is the last child … Read more
That’s the other way around. You should write: $(“table.planning_grid”).on({ mouseenter: function() { // Handle mouseenter… }, mouseleave: function() { // Handle mouseleave… }, click: function() { // Handle click… } }, “td”);
Quick answer : append the form to the body. document.body.appendChild(form); Or, if you’re using jQuery as above: $(document.body).append(form); Details : According to the HTML standards, if the form is not associated to the browsing context(document), the form submission will be aborted. HTML SPEC see 4.10.21.3.2 In Chrome 56, this spec was applied. Chrome code diff … Read more
It’s pretty clear in the docs why you wouldn’t want to use live. Also as mentioned by Felix, .on is a more streamline way of attaching events. Use of the .live() method is no longer recommended since later versions of jQuery offer better methods that do not have its drawbacks. In particular, the following issues … Read more
The on documentation states (in bold ;)): Event handlers are bound only to the currently selected elements; they must exist on the page at the time your code makes the call to .on(). Equivalent to .live() would be something like $(document.body).on(‘change’, ‘select[name^=”income_type_”]’, function() { alert($(this).val()); }); Although it is better if you bind the event … Read more