title: Selector regression after upgrade to jQuery 1.3.2
body: <p>I've recently upgraded an application from jQuery 1.2 to 1.3.2 - and we've found a rather strange regression.</p>
  
  <p>For some html approximately like this (simplified a bit)</p>
  
  <pre><code>&lt;div id="steps"&gt;
    &lt;div class="step"&gt;
      &lt;span&gt;step #1&lt;/span&gt;
      &lt;div class="removeStep"&gt; X &lt;/div&gt;
    &lt;/div&gt;
    &lt;div class="step"&gt;
      &lt;span&gt;step #2&lt;/span&gt;
      &lt;div class="removeStep"&gt; X &lt;/div&gt;
    &lt;/div&gt;
  &lt;/div&gt;
  </code></pre>
  
  <p>We previously attached an event like so, for all the steps:</p>
  
  <pre><code>$("#steps").find(".removeStep").click(removeStepFunc)
  </code></pre>
  
  <p>Under 1.2 this would find all the steps, even ones we dynamically added.  Under 1.3 this only ever finds the first step.</p>
  
  <p>This also doesn't work:</p>
  
  <pre><code>#("#steps .removeStep").click(removeStepFunc)
  </code></pre>
  
  <p>However, this does:</p>
  
  <pre><code>#("#steps).children().find(".removeStep").click(removeStepFunc)
  </code></pre>
  
  <p>I can obviously work around the issue, but It does make me a little nervous that perhaps there are other similar regressions affecting the application now we have upgraded, that will only present themselves in some cases when we have more then one element to match.</p>
  
  <p>Also I see this other question, which I suspect might be the same issue?</p>
  
  <p><a href="https://stackoverflow.com/questions/969647/jquery-selector-bug-composed-selector-vs-simple-selector-find">jQuery selector bug? composed selector vs. simple selector &amp; find()</a></p>