Alright well it's not necessarily a Mootools problem as the code I have whipped up works. Basically I am trying to do this: 1) Have a form where a user can submit some pricing information with Ajax. This info is sent to the database and then a response is sent back like: [x] Name - $100.00 Code (markup): Where [x] is a JavaScript link. 2) After the user has input a few prices they have the option of clicking the little [x] (let's call this the 'remove' link) which sends another Ajax request and removes the respective price. Here is the code I am using: //once the dom is ready window.addEvent('domready', function() { $('add_price').addEvent('click', function(event) { //prevent the page from changing event.stop(); // get variables var name = $('pricing_name').get('value'); //make the ajax call, replace text var url = 'ajax/add_price.php?price=' + $('pricing_cost').get('value') + '&name=' + $('pricing_name').get('value'); var pricing = $('pricing').get('html'); var request = new Request({ url: url, method:'post', onRequest: function() { }, onComplete: function(response) { $('pricing').set('html', pricing + response); } }).send(); }); }); window.addEvent('domready', function() { $$('.remove').each(function(el) { //add click event el.addEvent('click', function(e) { title = el.get('title'); var url = 'ajax/remove_price.php?id=' + title; var pricing = $('pricing').get('html'); var request = new Request({ url: url, method:'post', onRequest: function() { }, onComplete: function(response) { $('pricing').set('html', 'test' + response); } }).send(); }); }); }); Code (markup): When tested outside of an Ajax call the above JavaScript works. However, when a link (say the 'remove' link) is sent through an Ajax response then it doesn't function at all. No errors are reported either. I've worked with JavaScript previously, and ran into a similar problem before. My solution was to use eval() to execute the javascript when it was passed through Ajax. However, it is my understanding that Mootools is non obtrusive and therefore shouldn't be affected by an ajax call . . . however, I have a slight inclination that it's due to the fact that the page was already rendered before the ajax call. Anyway, any help would be greatly appreciated!