I know it's a pain in the arse so I won't whine. I'll try to look at the code and see if I can help in that area, I feel intuitively like it's a feature that just requires some elbow grease up front before the code is too mature to break backwards compatibility. Without contributing a solution I'm happy with the engine's proposed goal, which it apparently follows though with.
On Sat, Nov 1, 2008 at 9:44 PM, John Resig <[EMAIL PROTECTED]> wrote: > > Unfortunately, at this point, that's not really happening. The > querySelectorAll method (of the Selectors API specification) does not > include support for namespaces - thus it's very likely that JavaScript > libraries won't support it going forward. > > One thing that I'd like to fix (and I haven't checked, yet, to see how > it works in Sizzle) is to make "div" match both <div/> and <foo:div/> > elements. At the very least that would allow XML documents to become > sort-of usable. > > --John > > > > On Sat, Nov 1, 2008 at 9:41 PM, chris thatcher > <[EMAIL PROTECTED]> wrote: > > One thing Id like to ask about Sizzle is if it solves some of the simpler > > namespace/xml issues that seemed none intuitive in jquery's selector > > engine? In general my issue has to do with being able to more easily > take > > advantage of extension points in the xhtml specification to use valid > > namespaced attributes to build jquery extensions, for example > markup-aware > > templating like mjt (but built on jquery to reduce size, improve power > etc). > > > > Thanks > > Thatcher > > > > On Sat, Nov 1, 2008 at 8:37 PM, chris thatcher > > <[EMAIL PROTECTED]> wrote: > >> > >> You are probably aware that FF2 fails a few but thought I'd just post it > >> back in case others are curious: > >> > >> 5. selector module: class (3, 13, 16) > >> ... > >> 12. Escaped Class (.test\.foo\[5\]bar) expected: [ > span#test.foo[5]bar > >> ] result: [ ] > >> ... > >> 14. Descendant scaped Class (div .test\.foo\[5\]bar) expected: [ > >> span#test.foo[5]bar ] result: [ ] > >> ... > >> 16. Child escaped Class (form > .test\.foo\[5\]bar) expected: [ > >> span#test.foo[5]bar ] result: [ ] > >> ... > >> > >> Anyway, good work on sizzle, and it's nice to see a broad base of the > >> community being open to standardizing on it. > >> > >> Thatcher > >> > >> On Sat, Nov 1, 2008 at 6:33 PM, Dan Switzer <[EMAIL PROTECTED]> > >> wrote: > >>> > >>> John, > >>> > >>> On Sat, Nov 1, 2008 at 3:02 PM, John Resig <[EMAIL PROTECTED]> wrote: > >>>> > >>>> 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/ > >>> > >>> It passes the test in the above link. It failed when I downloaded the > GIT > >>> package and ran it locally. Perhaps the GIT repository is out-of-date. > >>> > >>> -Dan > >>> > >>> > >> > >> > >> > >> -- > >> Christopher Thatcher > > > > > > > > -- > > Christopher Thatcher > > > > > > > > > > > -- Christopher Thatcher --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
