John, I have gone through it again and looked at source code. I now got the problem you are talking about in your message...
...parent[ doneName]... (gasp) and I know the related problem there is in that part of selectors to be able to do that fast enough. But really you don't need to do that, not in the nth child resolution at least, that is the only place I use it in my NWMatcher. I find that hardly acceptable for "bind()" were fewer events are fired, I'm try to imagine what will happen in live() with virtually hundreds of triggering for second with just few events bound. Maybe you can take some ideas from NWMatcher on that specific part. I also bet that part slows down a bit your overall fast Sizzle. Diego On 30 Gen, 23:59, John Resig <jere...@gmail.com> wrote: > > Also this may have nothing to do with the original problem above I > > believe it is quite a big issue that must be addressed ! > > Well, this has to do with caching results for some selectors (with > deep selectors like "div p", for example). It's not really clear where > they should be managed - but the properties will need to be created in > some capacity. I have this on my todo list to resolve in some way > before Sizzle final is released. > > --John --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to jquery-dev@googlegroups.com To unsubscribe from this group, send email to jquery-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en -~----------~----~----~----~------~----~------~--~---
