Why does jQuery have to connect properties of future elements to a user based event, as opposed to it just listening and actioning?
<p>I'm really at the end of my tether on this one. For the last few weeks I have bumped into this issue continuously and I'm starting to wonder why this isn't a really basic aspect of jQuery.</p>

<p>All i want is for jQuery to listen for future elements and do things to them.</p>

<p><em>But</em></p>

<p>Without me having to correspond it to <em>any</em> events!</p>

<p>.live() wants an event to do things.</p>

<p>Surely there is something like live but where i can just say:</p>

<pre><code>$('div').live(function() {
    //just do stuff to current and future elements 
    //without me having to initiate it with events
});
</code></pre>

<p>The reason for needing this is that i have posts being dynamically loaded via another <em>javascript</em> file. If it was jQuery, i could just listen to it and give an event.</p>

<p><a href="http://marckremers.com/syndex/js/jquery.infinitescrollfortumblr.js" rel="nofollow">This</a> is the javascript file that loads the new content.
<a href="http://marckremers.com/syndex/js/jquery.syndex.js" rel="nofollow">This</a> is the jquery file where I need to add the behaviour.</p>

<hr>

<p>Edit: it's for this site <a href="http://syndex.me" rel="nofollow">http://syndex.me</a> But i don't think it's totally needed for the question. Cheers</p>

<p>=======</p>
