Are you sure that's Firefox 3 and not Firefox 3.1? Because I can get that selector to fail in 3.1 but not in 3.0 (that's the error that I was referring to in my email). Right now Mozilla appears to have mis-implemented the CSS :enabled selector (or, at least, implemented it differently from other browsers). Unfortunately there doesn't appear to be any consensus on what actually should be matched by the selector amongst browser vendors. Because of this we're going to see similar bugs pop up because of querySelectorAll.
Test suite: http://ejohn.org/apps/sizzle/test/ --John On Sat, Nov 1, 2008 at 1:34 PM, Dan Switzer <[EMAIL PROTECTED]> wrote: > John, > > In FF 3.0.3, I had the following fail for me: > > selector module: pseudo (:) selectors (1, 33, 34) > Enabled UI Element (#form input:enabled) expected: [ input#text1, > input#radio1, input#radio2, input#check1, input#check2, input#hidden2, > input#name ] result: [ input#text1, input#radio1, input#radio2, > input#check1, input#check2, input#hidden1, input#hidden2, input#name ] > > -Dan > > On Sat, Nov 1, 2008 at 1:26 PM, Karl Swedberg <[EMAIL PROTECTED]> wrote: >> >> Congratulations on nearing completion of this fantastic selector engine, >> John! Very exciting stuff. >> >> --Karl >> >> >> On Nov 1, 2008, at 11:37 AM, John Resig wrote: >> >> Hey Everyone - >> >> I've been working on a new selector engine for jQuery on-and-off again >> these past couple months and I finally have something ready to land: >> http://dev.jquery.com/ticket/3563 >> >> I've been working on the code for this project over here: >> http://github.com/jeresig/sizzle/tree/master >> >> (The end goal is to have this become the new default selector engine >> in a number of libraries - Prototype, MochiKit, Dojo, and TinyMCE have >> all expressed interest in using it, as well.) >> >> It passes the test suite in Firefox 3, Safari 3.1, and IE 6. There is >> one minor bug in Firefox 3.1 and another minor one in Opera 9.6 - both >> of which are specific browser bugs (and I'm filing appropriately) and >> neither of which are show stoppers. >> >> It's a considerable boost in performance over what we have now, in >> jQuery. I'll go into specific details later (once we're sure that >> there's no major bugs). >> >> Let me know if you have any questions and I'll be happy to answer them >> (although I'll be going out of town tomorrow for a week). >> >> --John >> >> >> >> >> >> > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en -~----------~----~----~----~------~----~------~--~---
