Those aren't nested ids. The comma separates it into two (effectively) separate queries
ul#loginSection li#emilyLogin:not(.loggedIn) ul#loginSection li#joeLogin:not(.loggedIn) and should join the results. - Richard On Wed, Jan 14, 2009 at 11:42 PM, James Van Dyke <jame...@gmail.com> wrote: > > Try > > $("#emilyLogin:not(.loggedIn), #joeLogin:not(.loggedIn)").click( > function(){} > ); > > I'm thinking that the nested IDs are causing issues that the new > selector engine can't handle. Since IDs are supposed to be unique per > page, listing a hierarchy is unnecessary. Multiple IDs on a page > would violate W3C standards. > > > > On Jan 14, 3:32 pm, "Joe Morgan" <thewast...@gmail.com> wrote: > > Hello, > > > > When I attempt to upgrade my site from 1.2.6 to 1.3, I get an > unresponsive > > script error that causes my browser (both IE7 and FF3) to hang if the > script > > is not stopped. > > > > I've tracked down the bit of script causing the problem: > > $("ul#loginSection li#emilyLogin:not(.loggedIn), ul#loginSection > > li#joeLogin:not(.loggedIn)").click( > > function(){} > > ); > > As you can see, the problem exists even when the function defined for the > > click event is empty, leading me to wonder if it is some problem in the > CSS > > selector that is being used, given the engine changes from 1.2.6 to 1.3. > Am > > I doing something incorrectly? > > > > - Joe >