On 10/5/06, Arnar Birgisson <[EMAIL PROTECTED]> wrote: > I read somewhere that it supports CSS3 and below (don't know if that's > true) - cssQuery is said to support *some* CSS3 selectors. Any > specific reason you find cssQuery better? No - I has been around for awhile, and I didn't know about prototype's implementation (Wonder how I missed that actually). Are there any limitations to prototype's implementation ? Even if there is, I think size justifies it, sompared to cssQuery. I'm currently using a home-brewed function, which only supports tagname + classname|id - I would definately like to see a proper css selector for mochikit.
> The point is, the prototype code for this is not too long (4.5K) - > http://dev.rubyonrails.org/browser/spinoffs/prototype/src/selector.js > - would this be considered for inclusion in MochiKit if I ported it? > > Arnar > > On 10/5/06, troels knak-nielsen <[EMAIL PROTECTED]> wrote: > > cssQuery is the best implementation I've seen, and it works nicely > > together with mochikit. It's a bit heavyweight too though : > > http://dean.edwards.name/my/cssQuery/ > > > > On 10/5/06, Arnar Birgisson <[EMAIL PROTECTED]> wrote: > > > > > > Hi all, > > > > > > Many javascript libraries have convenience functions for selecting > > > elements with the CSS selector syntax (like prototypes $$ I'm told). > > > Has anyone implemented something like that with MochiKit? Preferably > > > supporting CSS3 selectors? > > > > > > Would you consider such a function a valuable addition to MochiKit? > > > > > > Arnar > > > > > > > > > > > > > > > > > > -- > > troels > > > > -- troels --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MochiKit" 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/mochikit -~----------~----~----~----~------~----~------~--~---
