Cycling Event Listeners vs many Listeners
<p>I'm doing some work with a program that has quite a lot to click, however somethings only need to be clicked when say their parent has been clicked on and is active. Now there are three ways as I see it to approach this.</p>

<ol>
<li>Many event handlers</li>
<li>Constantly Create and Destroy them</li>
<li>Have one top-level handler and read the Event for what child even occurred on (event.target)</li>
</ol>

<p>The reason three is not the most obvious choice for me is that children of what I clicked would be <code>event.target</code> and <code>object.parentNode</code> would need to repeatedly run to see what element was in-fact available for clicking; I hear DOM api's are expensive.</p>

<p>I'm interested to know how expensive each method is relative to each other and what is accepted practice in something like that. Number of listeners is in the hundreds range, it's a dynamic application with modest DOM mutation.</p>

<p><strong>EDIT:</strong> For clarification this question is about DIV's and attaching event handlers to them.</p>
